@sassoftware/sas-score-mcp-serverjs 0.4.1-1 → 0.4.1-3

package/src/toolSet/scrInfo.js

@@ -35,7 +35,7 @@ Examples
     name: 'scr-info',
     description: description,
     inputSchema: z.object({
-      url: z.string(),
+      url: z.string()
     }),
     handler: async (params) => {
       let {url, _appContext} = params;

package/src/toolSet/scrScore.js

@@ -1,69 +1,71 @@
-/*
- * Copyright © 2025, SAS Institute Inc., Cary, NC, USA.  All Rights Reserved.
- * SPDX-License-Identifier: Apache-2.0
- */
-
-import { z } from 'zod';
-import _scrScore from '../toolHelpers/_scrScore.js';
-
-function scrScore(_appContext) {
-  let description = `
-## scr-score
-
-Purpose
-Score a scenario using a model deployed as a SCR container  in Azure or another host).
-
-Inputs
-- url (string, required): SCR model identifier (URL)
-- scenario (string | object | array, optional): Input values to score. Accepts:
-  - a comma-separated key=value string (e.g. "x=1, y=2"),
-  - a JSON object with field names and values (recommended for typed inputs),
-  - an array of objects for batch scoring. If omitted, the tool will return the model's input variable definitions.
-
-What it returns
-- When scoring: the SCR endpoint response (predictions, probabilities, scores) merged with or alongside the supplied inputs.
-- When \`scenario\` is omitted: metadata describing the model's input variables (names, types, required/optional).
-
-Usage notes
-- Run \`scr-info\` first to inspect the expected input variables and types.
-- Prefer structured objects for numeric/date values to avoid type ambiguity; the simple string parser keeps values as strings.
-- Ensure network connectivity and any required credentials for the target SCR service.
-
-Examples
-- scrScore with url="loan" and scenario="age=45, income=60000"
-- scrScore with url="https://scr-host/models/loan" and scenario={age:45, income:60000}
-`;
-
-  let spec = {
-    name: 'scr-score',
-    description: description,
-    inputSchema: z.object({
-      url: z.string(),
-      scenario: z.any()
-    }),
-    handler: async (params) => {
-      let {url, scenario,_appContext} = params;
-  
-      if (url === null) {
-        return { status: { statusCode: 2, msg: `SCR model ${url} was not specified` }, results: {} };
-      }
-
-      // Normalize simple string scenarios like "x=1, y=2" into an object
-      if (typeof scenario === 'string' && scenario.includes('=')) {
-        scenario = scenario.split(',').reduce((acc, pair) => {
-          const [k, ...rest] = pair.split('=');
-          if (!k) return acc;
-          acc[k.trim()] = rest.join('=').trim();
-          return acc;
-        }, {});
-      }
-
-      let r = await _scrScore({ url: url, scenario: scenario , _appContext: _appContext});
-      return r;
-    }
-  }
-
-  return spec;
-}
-
+/*
+ * Copyright © 2025, SAS Institute Inc., Cary, NC, USA.  All Rights Reserved.
+ * SPDX-License-Identifier: Apache-2.0
+ */
+
+import { z } from 'zod';
+import _scrScore from '../toolHelpers/_scrScore.js';
+
+function scrScore(_appContext) {
+  let description = `
+## scr-score
+
+Purpose
+Score a scenario using a model deployed as a SCR container  in Azure or another host).
+
+Inputs
+- url (string, required): SCR model identifier (URL)
+- scenario (string | object | array, optional): Input values to score. Accepts:
+  - a comma-separated key=value string (e.g. "x=1, y=2"),
+  - a JSON object with field names and values (recommended for typed inputs),
+  - an array of objects for batch scoring. If omitted, the tool will return the model's input variable definitions.
+
+What it returns
+- When scoring: the SCR endpoint response (predictions, probabilities, scores) merged with or alongside the supplied inputs.
+- When \`scenario\` is omitted: metadata describing the model's input variables (names, types, required/optional).
+
+Usage notes
+- Run \`scr-info\` first to inspect the expected input variables and types.
+- Prefer structured objects for numeric/date values to avoid type ambiguity; the simple string parser keeps values as strings.
+- Ensure network connectivity and any required credentials for the target SCR service.
+
+Examples
+- scrScore with url="loan" and scenario="age=45, income=60000"
+- scrScore with url="https://scr-host/models/loan" and scenario={age:45, income:60000}
+`;
+
+  let spec = {
+    name: 'scr-score',
+    description: description,
+    inputSchema: z.object({
+      url: z.string(),
+      scenario: z.string()
+       
+    }),
+    
+    handler: async (params) => {
+      let {url, scenario,_appContext} = params;
+  
+      if (url === null) {
+        return { status: { statusCode: 2, msg: `SCR model ${url} was not specified` }, results: {} };
+      }
+
+      // Normalize simple string scenarios like "x=1, y=2" into an object
+      if (typeof scenario === 'string' && scenario.includes('=')) {
+        scenario = scenario.split(',').reduce((acc, pair) => {
+          const [k, ...rest] = pair.split('=');
+          if (!k) return acc;
+          acc[k.trim()] = rest.join('=').trim();
+          return acc;
+        }, {});
+      }
+
+      let r = await _scrScore({ url: url, scenario: scenario , _appContext: _appContext});
+      return r;
+    }
+  }
+
+  return spec;
+}
+
 export default scrScore;

package/src/toolSet/setContext.js

@@ -1,65 +1,65 @@
-/*
- * Copyright © 2025, SAS Institute Inc., Cary, NC, USA.  All Rights Reserved.
- * SPDX-License-Identifier: Apache-2.0
- */
-
-import {z} from 'zod';
-
-function setContext(_appContext) {
-    let description = `
-set-context — set the CAS and SAS server contexts for subsequent tool calls.
-
-USE when: switch to CAS server, change compute context, check current context, set both
-DO NOT USE for: get variables (use get-env), read data (use read-table), run programs (use run-sas-program)
-
-PARAMETERS
-- cas: string — CAS server name (optional), e.g. 'cas-shared-default', 'finance-cas-server'
-- sas: string — SAS compute context (optional), e.g. 'SAS Studio Compute Context', 'batch-compute'
-
-ROUTING RULES
-- "use finance-cas-server" → { cas: "finance-cas-server" }
-- "switch to SAS Studio Compute Context" → { sas: "SAS Studio Compute Context" }
-- "use finance-cas for CAS and batch-compute for SAS" → { cas: "finance-cas", sas: "batch-compute" }
-- "what context am I using" → { } (no params, returns current)
-
-EXAMPLES
-- "use finance-cas-server" → { cas: "finance-cas-server" }
-- "switch to batch-compute" → { sas: "batch-compute" }
-- "what's my current context" → { }
-
-NEGATIVE EXAMPLES (do not route here)
-- "read table cars" (use read-table)
-- "what's the value of X" (use get-env)
-- "run program" (use run-sas-program)
-
-ERRORS
-Returns current or updated context values {cas, sas}. Error if server not found or invalid name.
-  `;
-  
-    let spec = {
-    name: 'set-context',
-    description: description,
-        inputSchema: z.object({
-            cas: z.string(),
-            sas: z.string()
-        }),
-    handler: async (params) => {
-            
-            let {cas, sas} = params;
-            if (typeof cas === 'string' && cas.trim().length > 0) {
-                _appContext.contexts.cas = cas.trim();
-            }
-            if (typeof sas === 'string' && sas.trim().length > 0) {
-                _appContext.contexts.sas = sas.trim();
-            }
-            // Return a structured response without extraneous keys
-            return {
-                content: [{ type: 'text', text: JSON.stringify(_appContext.contexts) }],
-                structuredContent: _appContext.contexts
-            };
-        }
-    }
-    return spec;
-}
-export default setContext;
-
+/*
+ * Copyright © 2025, SAS Institute Inc., Cary, NC, USA.  All Rights Reserved.
+ * SPDX-License-Identifier: Apache-2.0
+ */
+
+import {z} from 'zod';
+
+function setContext(_appContext) {
+    let description = `
+set-context — set the CAS and SAS server contexts for subsequent tool calls.
+
+USE when: switch to CAS server, change compute context, check current context, set both
+DO NOT USE for: get variables (use get-env), read data (use read-table), run programs (use run-sas-program)
+
+PARAMETERS
+- cas: string — CAS server name (optional), e.g. 'cas-shared-default', 'finance-cas-server'
+- sas: string — SAS compute context (optional), e.g. 'SAS Studio Compute Context', 'batch-compute'
+
+ROUTING RULES
+- "use finance-cas-server" → { cas: "finance-cas-server" }
+- "switch to SAS Studio Compute Context" → { sas: "SAS Studio Compute Context" }
+- "use finance-cas for CAS and batch-compute for SAS" → { cas: "finance-cas", sas: "batch-compute" }
+- "what context am I using" → { } (no params, returns current)
+
+EXAMPLES
+- "use finance-cas-server" → { cas: "finance-cas-server" }
+- "switch to batch-compute" → { sas: "batch-compute" }
+- "what's my current context" → { }
+
+NEGATIVE EXAMPLES (do not route here)
+- "read table cars" (use read-table)
+- "what's the value of X" (use get-env)
+- "run program" (use run-sas-program)
+
+ERRORS
+Returns current or updated context values {cas, sas}. Error if server not found or invalid name.
+  `;
+  
+    let spec = {
+    name: 'set-context',
+    description: description,
+        inputSchema: z.object({
+      cas: z.string().optional(),
+      sas: z.string().optional()
+    }),
+    handler: async (params) => {
+            
+            let {cas, sas} = params;
+            if (typeof cas === 'string' && cas.trim().length > 0) {
+                _appContext.contexts.cas = cas.trim();
+            }
+            if (typeof sas === 'string' && sas.trim().length > 0) {
+                _appContext.contexts.sas = sas.trim();
+            }
+            // Return a structured response without extraneous keys
+            return {
+                content: [{ type: 'text', text: JSON.stringify(_appContext.contexts) }],
+                structuredContent: _appContext.contexts
+            };
+        }
+    }
+    return spec;
+}
+export default setContext;
+

package/src/toolSet/superstat.js

@@ -1,59 +1,61 @@
-/*
- * Copyright © 2025, SAS Institute Inc., Cary, NC, USA.  All Rights Reserved.
- * SPDX-License-Identifier: Apache-2.0
- */
-import _submitCode from '../toolHelpers/_submitCode.js';
-import { z } from 'zod';
-
-function superstat(_appContext) {
-  let desc = `
-  ## superstat:  compute superstat for two numbers using SAS programming 
-
-  ## Details
-  This is a tool to demonstrate using SAS programming to score. The SAS program for suprestat is
-  below. In a real application this would be a more complex program that is 
-  available to the SAS server.
-
-  
-    ods html style=barrettsblue;  
-    data temp;
-    superstat = (&a + &b) * 42;
-    run;
-    proc print data=temp;
-    run;
-    ods html close; 
-    run;
-  
-  ## Sample Prompt
-
-    - compute superstat for 1 and 2
-    - compute superstat for 3,5
-    
-    `;
-  let spec = {
-    name: 'superstat',
-    description: desc,
-    inputSchema: z.object({
-      a: z.number(),
-      b: z.number()
-    }),
-    handler: async (params) => {
-      let src = `
-          ods html style=barrettsblue;  
-          data temp;
-          superstat = (&a + &b) * 42;
-          run;
-          proc print data=temp;
-          run;
-          ods html close; 
-          run;
-          `;
-      params.src = src;
-      let r = await _submitCode(params);
-      return r;
-    }
-
-  };
-  return spec;
-}
-export default superstat;
+/*
+ * Copyright © 2025, SAS Institute Inc., Cary, NC, USA.  All Rights Reserved.
+ * SPDX-License-Identifier: Apache-2.0
+ */
+import { type } from 'node:os';
+import _submitCode from '../toolHelpers/_submitCode.js';
+import { z } from 'zod';
+
+function superstat(_appContext) {
+  let desc = `
+  ## superstat:  compute superstat for two numbers using SAS programming 
+
+  ## Details
+  This is a tool to demonstrate using SAS programming to score. The SAS program for suprestat is
+  below. In a real application this would be a more complex program that is 
+  available to the SAS server.
+
+  
+    ods html style=barrettsblue;  
+    data temp;
+    superstat = (&a + &b) * 42;
+    run;
+    proc print data=temp;
+    run;
+    ods html close; 
+    run;
+  
+  ## Sample Prompt
+
+    - compute superstat for 1 and 2
+    - compute superstat for 3,5
+    
+    `;
+  let spec = {
+    name: 'superstat',
+    description: desc,
+    inputSchema: z.object({
+      a: z.number().optional()
+    }),
+      required: ['a', 'b']
+    },
+    handler: async (params) => {
+      let src = `
+          ods html style=barrettsblue;  
+          data temp;
+          superstat = (&a + &b) * 42;
+          run;
+          proc print data=temp;
+          run;
+          ods html close; 
+          run;
+          `;
+      params.src = src;
+      let r = await _submitCode(params);
+      return r;
+    }
+
+  };
+  return spec;
+}
+export default superstat;

package/src/toolSet/tableInfo.js

@@ -1,57 +1,57 @@
-/*
- * Copyright © 2025, SAS Institute Inc., Cary, NC, USA.  All Rights Reserved.
- * SPDX-License-Identifier: Apache-2.0
- */
-import { z } from 'zod';
-import debug from 'debug';
-
-import _tableInfo  from '../toolHelpers/_tableInfo.js';
-function tableInfo(_appContext) {
-
-     let describe = `
-table-info — retrieve metadata about a table in a CAS or SAS library.
-
-USE when: what columns, describe structure, show schema, table statistics, column info
-DO NOT USE for: read data (use read-table), list tables (use list-tables), find table (use find-table), queries (use sas-query)
-
-PARAMETERS
-- table: string — table name (required)
-- lib: string — caslib or libref (required)
-- server: string (default: 'cas') — 'cas' or 'sas'
-
-ROUTING RULES
-- "what columns are in cars" → { table: "cars", lib: "<lib>", server: "cas" }
-- "describe table sales in Public" → { table: "sales", lib: "Public", server: "cas" }
-- "show schema for mylib.iris on sas" → { table: "iris", lib: "mylib", server: "sas" }
-
-EXAMPLES
-- "what columns in cars" → { table: "cars", lib: "<lib>", server: "cas" }
-- "describe structure of customers in Public" → { table: "customers", lib: "Public", server: "cas" }
-
-NEGATIVE EXAMPLES (do not route here)
-- "read table cars" (use read-table)
-- "list tables in Public" (use list-tables)
-- "does table exist" (use find-table)
-- "query table" (use sas-query)
-
-ERRORS
-Returns columns array (name, type, label, format, length) and tableInfo (rowCount, fileSize, created, modified).
-  `;
-   
-    let  specs = {
-      name: 'table-info',
-      description: describe,
-      inputSchema: z.object({
-        table: z.string(),
-        lib: z.string(),
-        server: z.string()
-      }),
-    handler: async (params) => {
-        params.describe = true;
-        let r = await _tableInfo(params);
-        return r;
-      }
-    }
-    return specs;
-}
-export default tableInfo;
+/*
+ * Copyright © 2025, SAS Institute Inc., Cary, NC, USA.  All Rights Reserved.
+ * SPDX-License-Identifier: Apache-2.0
+ */
+import { z } from 'zod';
+import debug from 'debug';
+
+import _tableInfo  from '../toolHelpers/_tableInfo.js';
+import { type } from 'node:os';
+function tableInfo(_appContext) {
+
+     let describe = `
+table-info — retrieve metadata about a table in a CAS or SAS library.
+
+USE when: what columns, describe structure, show schema, table statistics, column info
+DO NOT USE for: read data (use read-table), list tables (use list-tables), find table (use find-table), queries (use sas-query)
+
+PARAMETERS
+- table: string — table name (required)
+- lib: string — caslib or libref (required)
+- server: string (default: 'cas') — 'cas' or 'sas'
+
+ROUTING RULES
+- "what columns are in cars" → { table: "cars", lib: "<lib>", server: "cas" }
+- "describe table sales in Public" → { table: "sales", lib: "Public", server: "cas" }
+- "show schema for mylib.iris on sas" → { table: "iris", lib: "mylib", server: "sas" }
+
+EXAMPLES
+- "what columns in cars" → { table: "cars", lib: "<lib>", server: "cas" }
+- "describe structure of customers in Public" → { table: "customers", lib: "Public", server: "cas" }
+
+NEGATIVE EXAMPLES (do not route here)
+- "read table cars" (use read-table)
+- "list tables in Public" (use list-tables)
+- "does table exist" (use find-table)
+- "query table" (use sas-query)
+
+ERRORS
+Returns columns array (name, type, label, format, length) and tableInfo (rowCount, fileSize, created, modified).
+  `;
+   
+    let  specs = {
+      name: 'table-info',
+      description: describe,
+      inputSchema: z.object({
+      table: z.string(),
+      lib: z.string().optional()
+    }),
+    handler: async (params) => {
+        params.describe = true;
+        let r = await _tableInfo(params);
+        return r;
+      }
+    }
+    return specs;
+}
+export default tableInfo;

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.