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

package/skills/mcp-tool-description-optimizer/references/examples.md

@@ -1,123 +0,0 @@
-# Before / After Examples
-
-## Example 1 — list-libraries (SAS Viya MCP)
-
-### BEFORE (~620 tokens)
-
-```
-## list-libraries — enumerate CAS or SAS libraries
-
-LLM Invocation Guidance (critical)
-Use THIS tool when the user asks for: "list libs", "list libraries", "show cas libs", "show sas libs",
-"what libraries are available", "list caslib(s)", "enumerate libraries", "libraries in cas", "libraries in sas".
-DO NOT use this tool when the user asks for: tables inside a specific library (choose listTables),
-columns/metadata of a table, job/program execution, models, or scoring.
-
-Trigger Phrase → Parameter Mapping
-- "cas libs" / "in cas" / "cas libraries" → { server: 'cas' }
-- "sas libs" / "in sas" / "base sas libraries" → { server: 'sas' }
-- "all libs" / "all libs" -> {server: 'all'}
-→ { server: 'all' }
-- "next" (after prior call) → { start: previous.start + previous.limit }
-- "first 20 cas libs" → { server: 'cas', limit: 20 }
-- If server unspecified: default to all.
-
-Parameters
-- server (cas|sas|all, default 'all')
-- limit (integer > 0, default 10)
-- start (1-based offset, default 1)
-- where (optional filter expression, default '')
-
-Response Contract
-Return JSON-like structure from helper; consumers may extract an array of library objects/names.
-If number of returned items === limit supply a pagination hint: start = start + limit.
-
-Behavior Summary
-- Pure listing; no side effects.
-- If ambiguous short request like "list" or "libs" and no prior context: assume { server: 'cas' }.
-- If user explicitly asks for ALL (e.g. "all cas libs") and count likely large, honor limit=50 unless
-  user supplies a value; include note about paging.
-
-Disambiguation Rules
-- If user mentions a singular library name plus desire for tables ("list tables in SASHELP") choose
-  listTables (not this tool).
-- If user mixes "tables" and "libraries" ask for clarification unless clearly about libraries.
-
-Examples
-- "list libraries" → { server: 'all', start:1, limit:10 }
-- "list libs" → { server: 'all', start:1, limit:10 }
-- "list sas libs" → { server: 'sas' }
-- "list cas libraries" → { server: 'cas' }
-- "show me 25 cas libraries" → { server:'cas', limit:25 }
-- "next" (after prior call {start:1,limit:10}) → { start:11, limit:10 }
-- "filter cas libs" (no criterion) → ask: "Provide a filter or continue without one?"
-
-Negative Examples (do not route here)
-- "list tables in public" (route to list-tables)
-- "list models, list tables, list jobs, list jobdef and similar request"
-- "describe library" (likely list-tables or table-info depending on follow-up)
-- "run program to make a lib" (run-sas-program tool)
-
-Error Handling
-- On backend error: return structured error with message field; do not hallucinate libraries.
-- Empty result set → return empty list plus (if start>1) a hint that paging may have exceeded available items.
-
-Rationale
-Concise, signal-rich description increases probability this spec is selected for generic library
-enumeration intents.
-```
-
-### AFTER (~210 tokens)
-
-```
-list-libraries — enumerate CAS or SAS libraries.
-
-USE when: list/show/enumerate libraries, caslibs, sas libs, available libraries
-DO NOT USE for: listing tables in a library (→ list-tables), column/table metadata, job execution, models, scoring
-
-PARAMETERS
-- server: 'cas' | 'sas' | 'all' (default: 'all')
-- limit: integer > 0 (default: 10)
-- start: 1-based offset (default: 1)
-- where: optional filter expression (default: '')
-
-ROUTING RULES
-- "cas libs / cas libraries / in cas"          → { server: 'cas' }
-- "sas libs / sas libraries / in sas"          → { server: 'sas' }
-- "all libs / all libraries"                   → { server: 'all' }
-- "all cas libs" with no limit given           → { server: 'cas', limit: 50 } + paging note
-- "next" after prior call (start:S, limit:L)   → { start: S + L, limit: L }
-- "filter cas libs" with no filter given       → ask: "What filter expression should I apply?"
-- server unspecified / ambiguous "list"/"libs" → { server: 'cas' }
-
-EXAMPLES
-- "list libraries"                → { server: 'all', start: 1, limit: 10 }
-- "list cas libraries"            → { server: 'cas', start: 1, limit: 10 }
-- "show me 25 sas libs"           → { server: 'sas', limit: 25, start: 1 }
-- "next" (prev: start:1,limit:10) → { server: <same>, start: 11, limit: 10 }
-
-NEGATIVE EXAMPLES (do not route here)
-- "list tables in SASHELP"        → list-tables
-- "list models / jobs / jobdefs"  → respective tools
-- "run a program to create a lib" → run-sas-program
-
-PAGINATION
-If returned count === limit → hint: next start = start + limit.
-If start > 1 and result empty → note paging may exceed available items.
-
-ERRORS
-Return structured error with message field. Never hallucinate library names.
-```
-
-**Token reduction: ~66%**
-
----
-
-## Key patterns illustrated
-
-- Trigger phrases consolidated from 3 blocks → 1 ROUTING RULES block
-- "Rationale", "Behavior Summary", "Response Contract" sections eliminated
-- Orphaned `→ { server: 'all' }` arrow removed
-- Parameter defaults made explicit inline
-- Examples trimmed to one line each
-- Negative examples now name the redirect tool explicitly

package/skills/sas-read-and-score/SKILL.md

@@ -1,91 +0,0 @@
----
-name: sas-read-and-score
-description: >
-  Guide the full read → score workflow in SAS Viya: reading records from a table (using read-table
-  or sas-query) and then scoring them with a MAS model (using model-score). Use this skill whenever
-  the user wants to score records from a table, run a model against query results, predict outcomes
-  for a set of rows, or any combination of fetching data and scoring it. Trigger phrases include:
-  "score these records", "score results of my query", "run the model on this table",
-  "predict for these customers", "fetch and score", "read and score", "score rows from",
-  "run model on table data", or any request that combines reading table data with model prediction.
----
-
-# SAS Read → Score Workflow
-
-Orchestrates the full two-step pattern of reading records from a SAS/CAS table and scoring them
-with a deployed MAS model.
-
-This skill chains two sub-skills:
-1. **sas-read-strategy** — Choose between `read-table` and `sas-query`
-2. **sas-score-workflow** — Validate model, invoke scoring, present results
-
----
-
-## Quick reference
-
-1. **Does the user already have data in hand?**
-   - Yes → skip to Step 2 (scoring)
-   - No → use `sas-read-strategy` to fetch data
-
-2. **Is the model name familiar?**
-   - Yes → proceed to score
-   - No → pause and use `find-model` / `model-info`
-
-3. **Invoke model-score** with the fetched data
-
-4. **Merge results** and present as a table
-
----
-
-## Common flows
-
-**Flow A — Score rows from a table directly**
-> "Score the first 10 customers in Public.customers with the churn model"
-
-1. Apply `sas-read-strategy` → use `read-table` to fetch 10 rows
-2. Apply `sas-score-workflow` → invoke `model-score` and present results
-
-**Flow B — Score results of an analytical query**
-> "Score high-value customers (spend > 5000) in mylib.sales with the fraud model"
-
-1. Apply `sas-read-strategy` → use `sas-query` for aggregation
-2. Apply `sas-score-workflow` → invoke `model-score` and present results
-
-**Flow C — User supplies scenario data directly**
-> "Score age=45, income=60000, region=South with the churn model"
-
-1. Skip read strategy
-2. Apply `sas-score-workflow` → invoke `model-score` and present result
-
-**Flow D — Model unfamiliar**
-> "Score Public.applicants with the creditRisk2 model"
-
-1. Model unfamiliar → use `find-model` to verify existence
-2. Apply `sas-read-strategy` to fetch data
-3. Apply `sas-score-workflow` to score
-
----
-
-## For detailed guidance
-
-- **Read strategy decisions?** See `sas-read-strategy` skill
-- **Scoring validation and presentation?** See `sas-score-workflow` skill
-
-**Flow D — Model unfamiliar**
-> "Score Public.applicants with the creditRisk2 model"
-
-1. Pause — "creditRisk2" is new
-2. Suggest: `find-model` to confirm it exists, `model-info` to get input variables
-3. Once confirmed → `read-table` + `model-score`
-
----
-
-## Error handling
-
-| Problem | Action |
-|---|---|
-| Table not found | Ask for correct lib.tablename |
-| Model not found | Suggest find-model |
-| Field name mismatch | Show mismatch, ask user to confirm mapping |
-| Scoring error | Return structured error, suggest model-info |
-| Empty read result | Tell user, ask if they want to adjust the query/filter |