@sassoftware/sas-score-mcp-serverjs 0.4.1-7 → 1.0.0

package/src/toolHelpers/getLogonPayload.js

@@ -53,7 +53,6 @@ async function igetLogonPayload(_appContext) {
       token: _appContext.bearerToken,
       tokenType: "Bearer",
     };
-    console.error("[Note] Bearer token in logonPayload ", _appContext.bearerToken);
     return logonPayload;
   }
 
@@ -122,4 +121,9 @@ async function igetLogonPayload(_appContext) {
     return null;
   }
 }
+
+function isExpired(expiresAt, skewSeconds = 60) {
+  return Date.now() >= (expiresAt - skewSeconds * 1000);
+}
+
 export default getLogonPayload;

package/src/toolHelpers/refreshToken.js

@@ -9,10 +9,11 @@ async function refreshToken(_appContext, params) {
   let url = `${host}/SASLogon/oauth/token`;
 
   let aconnect = {
-    ca: _appContext.contexts.viyaCert.ca,     // trust this CA
     rejectUnauthorized: false  // or false, if you really want to bypass checks
   }
-
+  if (_appContext.contexts.viyaCert != null && _appContext.contexts.viyaCert.ca != null) {
+    aconnect.ca = _appContext.contexts.viyaCert.ca;
+  }
   const agent = new Agent(aconnect);
 
   console.error('[Info] Refreshing token...', token);

package/src/toolHelpers/refreshTokenOauth.js

@@ -6,7 +6,7 @@
  //import getOpts from './getOpts.js';
  async function refreshTokenOauth(_appContext, oauthInfo ){
  
-    const url = `${process.env.VIYA_SERVER}/SASLogon/oauth/token`;
+   const url = `${_appContext.VIYA_SERVER}/SASLogon/oauth/token`;
     let opts = _appContext.contexts.appCert;
 
     const agent = new Agent({
@@ -23,10 +23,10 @@
     try {
       const response = await fetch(url, {
         method: 'POST',
+        dispatcher: agent,
         headers: {
           'Accept': 'application/json',
-          'Content-Type': 'application/x-www-form-urlencoded',
-          dispatcher: agent
+          'Content-Type': 'application/x-www-form-urlencoded'
         },
         body: body.toString()
       });

package/src/toolSet/.claude/settings.local.json

@@ -6,7 +6,8 @@
       "mcp__sasmcp__sas-score-model-info",
       "Bash(cp \"C:/dev/github/7-skill-integration/.claude/skills/sas-read-and-score/SKILL.md\" \"C:/dev/github/7-skill-integration/skills/sas-read-and-score/SKILL.md\")",
       "Bash(cp \"C:/dev/github/7-skill-integration/.claude/skills/sas-read-strategy/SKILL.md\" \"C:/dev/github/7-skill-integration/skills/sas-read-strategy/SKILL.md\")",
-      "Bash(cp \"C:/dev/github/7-skill-integration/.claude/skills/sas-score-workflow/SKILL.md\" \"C:/dev/github/7-skill-integration/skills/sas-score-workflow/SKILL.md\")"
+      "Bash(cp \"C:/dev/github/7-skill-integration/.claude/skills/sas-score-workflow/SKILL.md\" \"C:/dev/github/7-skill-integration/skills/sas-score-workflow/SKILL.md\")",
+      "WebSearch"
     ]
   }
 }

package/src/toolSet/findModel.js

@@ -9,7 +9,7 @@ import _listModels from '../toolHelpers/_listModels.js';
 
 function findModel(_appContext) {
   let description = `
-find-model — locate a specific model deployed to MAS (Model Aggregation Service).
+find-model — locate a specific MAS model deployed to MAS server 
 
 USE when: find model, does model exist, is model deployed, lookup model, verify model exists
 DO NOT USE for: list models (use list-models), model info/variables (use model-info), score model (use model-score), find table/job/lib (use respective tools), scr models (use scr-info/scr-score)

package/src/toolSet/findTable.js

@@ -17,7 +17,7 @@ DO NOT USE for: list tables (use list-tables), table schema/columns (use table-i
 PARAMETERS
 - lib: string (required) — library name (e.g., 'Public', 'sashelp')
 - name: string (required) — table name to locate
-- server: 'cas' | 'sas' (default: 'cas') — target environment
+- server: 'cas' | 'sas' . If not specified set it to 'cas' — target environment
 
 ROUTING RULES
 - "find table <name> in <lib>" → { lib: "<lib>", name: "<name>", server: "cas" }
@@ -47,9 +47,9 @@ Returns { tables: [] } if not found; { tables: [name, ...] } if found. Never hal
     name: 'find-table',
     description: description,
     inputSchema: z.object({
-      name: z.string(),
       lib: z.string(),
-      server: z.string().optional() // default server is 'cas'
+      name: z.string(),
+      server: z.string() 
     }),
     
     handler: async (params) => {

package/src/toolSet/modelScore.js

@@ -10,7 +10,7 @@ const log = debug('tools');
 
 function modelScore(_appContext) {
   let description = `
-model-score — score data using a deployed model on MAS.
+mas-score — score data using a deployed model on MAS.
 
 USE when: score with model, predict using model, batch scoring, model predictions
 DO NOT USE for: find model, model metadata, list models, run programs/jobs, query tables
@@ -40,7 +40,7 @@ Returns predictions, probabilities, scores merged with input data. Returns error
 
  
   let spec = {
-    name: 'model-score',
+    name: 'mas-score',
     description: description,
     inputSchema:z.object({
       model: z.string(),

package/src/toolSet/runJob.js

@@ -1,81 +1,81 @@
-/*
- * Copyright © 2025, SAS Institute Inc., Cary, NC, USA.  All Rights Reserved.
- * SPDX-License-Identifier: Apache-2.0
- */
-
-import { z } from 'zod';
-import _jobSubmit from '../toolHelpers/_jobSubmit.js';
-
-function runJob(_appContext) {
- 
-  let description = `
-run-job — execute a deployed SAS Viya job.
-
-USE when: run job, execute job, run with parameters
-DO NOT USE for: arbitrary SAS code (use run-sas-program), macros (use run-macro), list/find jobs
-
-PARAMETERS
-- name: string — job name (required)
-- scenario: string | object — input parameters. Accepts: "x=1, y=2" or {x:1, y:2}
-
-ROUTING RULES
-- "run job xyz" → { name: "xyz" }
-- "run job xyz with param1=10, param2=val2" → { name: "xyz", scenario: {param1:10, param2:"val2"} }
-
-EXAMPLES
-- "run job xyz" → { name: "xyz" }
-- "run job monthly_etl with month=10, year=2025" → { name: "monthly_etl", scenario: {month:10, year:2025} }
-
-NEGATIVE EXAMPLES (do not route here)
-- "run SAS code" (use run-sas-program)
-- "run macro X" (use run-macro)
-- "list jobs" (use list-jobs)
-- "find job X" (use find-job)
-
-ERRORS
-Returns log output, listings, tables from job. Error if job not found.
-`;
-
-  let spec = {
-    name: 'run-job',
-    description: description,
-    inputSchema: z.object({
-      name: z.string(),
-      scenario: z.string().optional()
-    }),
-    handler: async (params) => {
-      let scenario = params.scenario;
-      let scenarioObj = {};
-      let count = 0;
-      // 
-      if (scenario == null) {
-        scenarioObj = {};
-      } else if (typeof scenario === 'object') {
-        scenarioObj = scenario;
-      } else if (Array.isArray(scenario)) {
-        scenarioObj = scenario[0];
-      } else if (typeof scenario === 'string') {
-        if (scenario.trim() === '') {
-          scenarioObj = {};
-        } else {
-         // console.error('Incoming scenario', scenario);
-          scenarioObj = scenario.split(',').reduce((acc, pair) => {
-            let [key, value] = pair.split('=');
-            acc[key.trim()] = value;
-            count++;
-            return acc;
-          }, {});
-        }
-      }
-      params.type = 'job';
-      params.scenario = scenarioObj;
-      // Provide runtime context for auth and server settings
-      let r = await _jobSubmit(params);
-      return r;
-    }
-  };
-  return spec;
-}
-
-export default runJob;
-
+/*
+ * Copyright © 2025, SAS Institute Inc., Cary, NC, USA.  All Rights Reserved.
+ * SPDX-License-Identifier: Apache-2.0
+ */
+
+import { z } from 'zod';
+import _jobSubmit from '../toolHelpers/_jobSubmit.js';
+
+function runJob(_appContext) {
+ 
+  let description = `
+run-job — score with a deployed SAS Viya job.
+
+USE when: score with job, run job, execute job
+DO NOT USE for: arbitrary SAS code (use run-sas-program), macros (use run-macro), list/find jobs
+
+PARAMETERS
+- name: string — job name (required)
+- scenario: string | object — input parameters. Accepts: "x=1, y=2" or {x:1, y:2}
+
+ROUTING RULES
+- "run job xyz" → { name: "xyz" }
+- "run job xyz with param1=10, param2=val2" → { name: "xyz", scenario: {param1:10, param2:"val2"} }
+
+EXAMPLES
+- "run job xyz" → { name: "xyz" }
+- "run job monthly_etl with month=10, year=2025" → { name: "monthly_etl", scenario: {month:10, year:2025} }
+
+NEGATIVE EXAMPLES (do not route here)
+- "run SAS code" (use run-sas-program)
+- "run macro X" (use run-macro)
+- "list jobs" (use list-jobs)
+- "find job X" (use find-job)
+
+ERRORS
+Returns log output, listings, tables from job. Error if job not found.
+`;
+
+  let spec = {
+    name: 'run-job',
+    description: description,
+    inputSchema: z.object({
+      name: z.string(),
+      scenario: z.string().optional()
+    }),
+    handler: async (params) => {
+      let scenario = params.scenario;
+      let scenarioObj = {};
+      let count = 0;
+      // 
+      if (scenario == null) {
+        scenarioObj = {};
+      } else if (typeof scenario === 'object') {
+        scenarioObj = scenario;
+      } else if (Array.isArray(scenario)) {
+        scenarioObj = scenario[0];
+      } else if (typeof scenario === 'string') {
+        if (scenario.trim() === '') {
+          scenarioObj = {};
+        } else {
+         // console.error('Incoming scenario', scenario);
+          scenarioObj = scenario.split(',').reduce((acc, pair) => {
+            let [key, value] = pair.split('=');
+            acc[key.trim()] = value;
+            count++;
+            return acc;
+          }, {});
+        }
+      }
+      params.type = 'job';
+      params.scenario = scenarioObj;
+      // Provide runtime context for auth and server settings
+      let r = await _jobSubmit(params);
+      return r;
+    }
+  };
+  return spec;
+}
+
+export default runJob;
+

package/src/toolSet/runJobdef.js

@@ -1,82 +1,82 @@
-/*
- * Copyright © 2025, SAS Institute Inc., Cary, NC, USA.  All Rights Reserved.
- * SPDX-License-Identifier: Apache-2.0
- */
-
-import { z } from 'zod';
-import _jobSubmit from '../toolHelpers/_jobSubmit.js';
-
-function runJobdef(_appContext) {
-  // JSON object for LLM/tooling
- 
-  let description = `
-run-jobdef — execute a SAS Viya job definition.
-
-USE when: run jobdef, execute jobdef, run with parameters
-DO NOT USE for: arbitrary SAS code (use run-sas-program), macros (use run-macro), list/find jobdefs
-
-PARAMETERS
-- name: string — jobdef name (required)
-- scenario: string | object — input parameters. Accepts: "x=1, y=2" or {x:1, y:2}
-
-ROUTING RULES
-- "run jobdef xyz" → { name: "xyz" }
-- "run jobdef xyz with param1=10, param2=val2" → { name: "xyz", scenario: {param1:10, param2:"val2"} }
-
-EXAMPLES
-- "run jobdef xyz" → { name: "xyz" }
-- "run jobdef monthly_report with month=10, year=2025" → { name: "monthly_report", scenario: {month:10, year:2025} }
-
-NEGATIVE EXAMPLES (do not route here)
-- "run SAS code" (use run-sas-program)
-- "run macro X" (use run-macro)
-- "list jobdefs" (use list-jobdefs)
-- "find jobdef X" (use find-jobdef)
-
-ERRORS
-Returns log output, listings, tables from jobdef. Error if jobdef not found.
-  `;
- 
-  let spec = {
-    name: 'run-jobdef',
-    description: description,
-    inputSchema: z.object({
-      name: z.string(),
-      scenario: z.string().optional()
-    }),
-    handler: async (params) => {
-      let scenario = params.scenario;
-      let scenarioObj = {};
-      let count = 0;
-      // 
-      if (scenario == null) {
-        scenarioObj = {};
-      } else if (typeof scenario === 'object') {
-        scenarioObj = scenario;
-      } else if (Array.isArray(scenario)) {
-        scenarioObj = scenario[0];
-      } else if (typeof scenario === 'string') {
-        if (scenario.trim() === '') {
-          scenarioObj = {};
-        } else {
-         // console.error('Incoming scenario', scenario);
-          scenarioObj = scenario.split(',').reduce((acc, pair) => {
-            let [key, value] = pair.split('=');
-            acc[key.trim()] = value;
-            count++;
-            return acc;
-          }, {});
-        }
-      }
-      params.type = 'def';
-      params.scenario = scenarioObj;
-      // Provide runtime context for auth and server settings
-      let r = await _jobSubmit(params);
-      return r;
-    }
-  };
-  return spec;
-}
-
-export default runJobdef;
-
+/*
+ * Copyright © 2025, SAS Institute Inc., Cary, NC, USA.  All Rights Reserved.
+ * SPDX-License-Identifier: Apache-2.0
+ */
+
+import { z } from 'zod';
+import _jobSubmit from '../toolHelpers/_jobSubmit.js';
+
+function runJobdef(_appContext) {
+  // JSON object for LLM/tooling
+ 
+  let description = `
+run-jobdef — score with a deployed SAS Viya job definition.
+
+USE when: score with jobdef, run jobdef, execute jobdef
+DO NOT USE for: arbitrary SAS code (use run-sas-program), macros (use run-macro), list/find jobdefs
+
+PARAMETERS
+- name: string — jobdef name (required)
+- scenario: string | object — input parameters. Accepts: "x=1, y=2" or {x:1, y:2}
+
+ROUTING RULES
+- "run jobdef xyz" → { name: "xyz" }
+- "run jobdef xyz with param1=10, param2=val2" → { name: "xyz", scenario: {param1:10, param2:"val2"} }
+
+EXAMPLES
+- "run jobdef xyz" → { name: "xyz" }
+- "run jobdef monthly_report with month=10, year=2025" → { name: "monthly_report", scenario: {month:10, year:2025} }
+
+NEGATIVE EXAMPLES (do not route here)
+- "run SAS code" (use run-sas-program)
+- "run macro X" (use run-macro)
+- "list jobdefs" (use list-jobdefs)
+- "find jobdef X" (use find-jobdef)
+
+ERRORS
+Returns log output, listings, tables from jobdef. Error if jobdef not found.
+  `;
+ 
+  let spec = {
+    name: 'run-jobdef',
+    description: description,
+    inputSchema: z.object({
+      name: z.string(),
+      scenario: z.string().optional()
+    }),
+    handler: async (params) => {
+      let scenario = params.scenario;
+      let scenarioObj = {};
+      let count = 0;
+      // 
+      if (scenario == null) {
+        scenarioObj = {};
+      } else if (typeof scenario === 'object') {
+        scenarioObj = scenario;
+      } else if (Array.isArray(scenario)) {
+        scenarioObj = scenario[0];
+      } else if (typeof scenario === 'string') {
+        if (scenario.trim() === '') {
+          scenarioObj = {};
+        } else {
+         // console.error('Incoming scenario', scenario);
+          scenarioObj = scenario.split(',').reduce((acc, pair) => {
+            let [key, value] = pair.split('=');
+            acc[key.trim()] = value;
+            count++;
+            return acc;
+          }, {});
+        }
+      }
+      params.type = 'def';
+      params.scenario = scenarioObj;
+      // Provide runtime context for auth and server settings
+      let r = await _jobSubmit(params);
+      return r;
+    }
+  };
+  return spec;
+}
+
+export default runJobdef;
+

package/skills/mcp-tool-description-optimizer/SKILL.md

@@ -1,129 +0,0 @@
----
-name: mcp-tool-description-optimizer
-description: >
-  Optimize MCP (Model Context Protocol) tool descriptions for token efficiency and LLM routing accuracy.
-  Use this skill whenever a user shares a raw, verbose, or poorly structured MCP tool description and wants
-  it improved, rewritten, or reviewed. Trigger on phrases like: "optimize this tool description",
-  "rewrite my MCP tool description", "make this tool description more efficient", "clean up my tool spec",
-  "improve how Claude picks my tool", or when a user pastes a JavaScript/TypeScript tool description string
-  and asks for help with it. Also trigger when the user mentions token efficiency, tool routing,
-  or LLM disambiguation in the context of MCP servers.
----
-
-# MCP Tool Description Optimizer
-
-Rewrites verbose or poorly structured MCP tool descriptions into compact, signal-rich versions that
-improve LLM tool selection accuracy while reducing token usage.
-
-## Why this matters
-
-Claude and other LLMs select MCP tools based entirely on the `description` field. Descriptions that are
-too long, redundant, or badly structured waste context tokens and reduce routing precision.
-A well-optimized description:
-- States what the tool does and when to use it upfront
-- Eliminates redundancy (same info repeated across sections)
-- Uses a compact, scannable format (labeled blocks, not nested markdown)
-- Includes clear negative examples to prevent mis-routing
-- Keeps parameters terse — name, type, default, one-line purpose
-
----
-
-## Optimization Process
-
-### Step 1 — Analyze the input description
-
-Before rewriting, identify these problems in the original:
-
-| Problem | Example |
-|---|---|
-| **Redundancy** | Trigger phrases listed in 3+ places |
-| **Filler sections** | "Rationale", "Behavior Summary", "Response Contract" with no routing signal |
-| **Orphaned syntax** | Arrows (`→`) or bullets with no target |
-| **Overlong examples** | Long prose examples when one-liners suffice |
-| **Heavy markdown** | `##` headers for every minor point |
-| **Duplicated parameter docs** | Same param described in both a table and prose |
-
-Call out 2–4 of the most impactful issues before writing the new version.
-
-### Step 2 — Rewrite using the standard template
-
-Use this exact block structure for the output. Omit blocks that don't apply.
-
-```
-<tool-name> — <one-line purpose>.
-
-USE when: <comma-separated user intents or trigger phrases>
-DO NOT USE for: <comma-separated anti-patterns with → redirect where applicable>
-
-PARAMETERS
-- <name>: <type> (default: <val>) — <one-line purpose>
-...
-
-ROUTING RULES
-- "<trigger phrase>" → { param: value }
-- "<trigger phrase>" → { param: value }
-- <ambiguous case> → <ask for clarification | default behavior>
-
-EXAMPLES
-- "<user utterance>" → { param: value, ... }
-- "<user utterance>" → { param: value, ... }
-
-NEGATIVE EXAMPLES (do not route here)
-- "<user utterance>" → <correct tool>
-
-PAGINATION (include only if tool is paginated)
-If returned count === limit → hint: next start = start + limit.
-If start > 1 and result empty → note paging may exceed available items.
-
-ERRORS
-<One or two lines: return structure, hallucination policy>
-```
-
-### Step 3 — Apply these rules consistently
-
-**USE/DO NOT USE block**
-- Write as comma-separated inline list, not a bullet list
-- DO NOT USE entries should name the redirect tool in parentheses where known
-
-**ROUTING RULES block**
-- One rule per line; quote the trigger phrase; use `→ { }` for param mapping
-- Consolidate synonyms on one line: `"cas libs / cas libraries / in cas" → { server: 'cas' }`
-- List the default/fallback rule last
-
-**PARAMETERS block**
-- One line per param: `- name: type (default: val) — purpose`
-- Skip obvious params (e.g. don't explain what `limit` means if it's standard pagination)
-
-**EXAMPLES block**
-- Each example fits on one line
-- For "next page" examples, include the prior call's state inline: `"next" (prev: start:1, limit:10) → { start: 11, limit: 10 }`
-
-**NEGATIVE EXAMPLES block**
-- Only include when mis-routing is a real risk
-- Format: `"<utterance>" → <correct-tool-name>`
-
-**Tone**
-- Imperative, terse. No filler words ("Please note that...", "It is important to...")
-- Never include a "Rationale" or "Behavior Summary" section — if behavior matters, encode it as a rule
-
-### Step 4 — Validate before returning
-
-Check the rewritten description against this list:
-
-- [ ] No trigger phrase appears in more than one block
-- [ ] No orphaned `→` arrows or dangling bullets
-- [ ] Parameter defaults are stated explicitly
-- [ ] Negative examples cover the tool's most common mis-routing risks
-- [ ] Total length is ≤ 50% of the original (target: 30–40% reduction)
-
----
-
-## Output format
-
-Always return:
-
-1. **Analysis** — 2–4 bullet points naming the key issues found in the original
-2. **Rewritten description** — inside a JavaScript code block (matching the user's original code style)
-3. **Change summary** — a short table or bullet list of what changed and why
-
-See `references/examples.md` for before/after examples of real tool descriptions.