@sassoftware/sas-score-mcp-serverjs 0.4.1-18 → 0.4.1-19

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sassoftware/sas-score-mcp-serverjs",
-  "version": "0.4.1-18",
+  "version": "0.4.1-19",
   "description": "A mcp server for SAS Viya",
   "author": "Deva Kumar <deva.kumar@sas.com>",
   "license": "Apache-2.0",

package/skills/sas-read-strategy/SKILL.md

@@ -15,20 +15,24 @@ of the data operation. Determines which server contains the data and which retri
 
 ## Determine the server location
 
-Before retrieving data, verify the library and determine which server(s) contain the table:
+Before retrieving data, locate the table and determine which server contains it:
 
-**Step 1: Verify library existence**
-- Use `sas-find-library-smart` skill to check the library in CAS first, then SAS if needed
-- This establishes the correct server and uppercase convention for SAS libraries
-- Informs the user which server contains the library
+**Smart table lookup with server detection**
 
-**Step 2: Locate the specific table**
-- Use `sas-score-find-table` to check if the table exists in the library
-- Possible outcomes:
-  - If table exists **only in CAS** → set `server: "cas"`
-  - If table exists **only in SAS** → set `server: "sas"`
-  - If table exists **in both** → ask the user: *"The table exists in both CAS and SAS. Which server would you prefer to query from?"*
-  - If table exists **in neither** → inform user and suggest verifying the table name
+Use `sas-score-find-table` with intelligent server detection:
+
+1. **First attempt**: Check CAS server (`server: "cas"`)
+   - If table exists → return table and server to caller
+   - If table not found → proceed to step 2
+
+2. **Second attempt**: Check SAS server (`server: "sas"`)
+   - If table exists → return table and server to caller
+   - If table not found in either server → inform user and suggest verifying the library and table names
+
+**Possible outcomes:**
+- Table found in CAS → use `server: "cas"` for subsequent read operations
+- Table found in SAS → use `server: "sas"` for subsequent read operations
+- Table not found in either server → inform user: *"The table 'lib.table' was not found in CAS or SAS. Please verify the library and table names."*
 
 ---
 
@@ -55,6 +59,13 @@ Ask yourself: does the user already have the data in hand?
 
 **How:**
 ```
+sas-score-find-table({
+  lib: "libraryname",
+  table: "tablename",
+  server: "cas"  // start with CAS
+})
+// if not found, repeat with server: "sas"
+
 sas-score-read-table({
   table: "tablename",
   lib: "libraryname",
@@ -65,11 +76,11 @@ sas-score-read-table({
 ```
 
 **Rules:**
-- Always determine the server first using `sas-score-find-table`
+- Always determine the server first using `sas-score-find-table` with smart detection (CAS → SAS)
 - Keep batch size ≤ 50 rows unless the user explicitly requests more
 - If table name is missing, ask: *"Which table should I read from? (format: lib.tablename)"*
 - If library is missing, ask: *"Which library contains the table?"*
-- If table exists in both servers, ask user which to use
+- If table exists in both servers, prefer CAS (already determined by smart detection)
 - Return raw column values; do not transform or aggregate
 
 ---
@@ -83,6 +94,13 @@ sas-score-read-table({
 
 **How:**
 ```
+sas-score-find-table({
+  lib: "libraryname",
+  table: "tablename",
+  server: "cas"  // start with CAS
+})
+// if not found, repeat with server: "sas"
+
 sas-query({
   table: "lib.tablename",
   query: "user's natural language question",
@@ -91,8 +109,8 @@ sas-query({
 ```
 
 **Rules:**
-- Check which server(s) contain the table using `sas-score-find-table` first
-- If table exists in both CAS and SAS, ask user which to query from
+- Check which server contains the table using `sas-score-find-table` with smart detection (CAS → SAS) first
+- If table exists in CAS, query from CAS; if only in SAS, query from SAS
 - Parse the user's natural language question into a PROC SQL SELECT statement
 - Ensure SELECT statement is valid SQL syntax
 - Do not add trailing semicolons to the SQL string
@@ -129,11 +147,12 @@ sas-query({
 
 | Problem | Action |
 |---|---|
-| Library not found | Use `sas-find-library-smart` skill to verify the library exists |
-| Table not found in either server | Inform user and suggest checking the table name |
-| Table exists in both CAS and SAS | Ask: *"The table exists in both servers. Which would you prefer: CAS or SAS?"* |
-| Table exists only in one server | Use that server automatically in your request |
-| Table name missing entirely | Ask: *"Which table should I read from?"* |
+| Table not found in CAS | Try SAS server using `sas-score-find-table` with `server: "sas"` |
+| Table not found in either server | Inform user: *"The table 'lib.table' was not found in CAS or SAS. Please verify the library and table names."* |
+| Table exists only in CAS | Use `server: "cas"` automatically for read operations |
+| Table exists only in SAS | Use `server: "sas"` automatically for read operations |
+| Table name missing entirely | Ask: *"Which table should I read from? (format: lib.tablename)"* |
+| Library name missing | Ask: *"Which library contains the table?"* |
 | Ambiguous intent (raw vs aggregate) | Ask: *"Do you want individual rows or a summary by some field?"* |
 | Empty result | Inform user, ask to adjust filter or query |
 
@@ -141,7 +160,7 @@ sas-query({
 
 ## Integration with other skills
 
-- **Before this skill**: Use `sas-find-library-smart` to verify and locate the library
+- **Before this skill**: Use `sas-score-find-table` to verify the table exists and determine the server location
 - **After this skill**: Use `sas-read-and-score` to score the retrieved data
 
 ---

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" }
@@ -49,7 +49,7 @@ Returns { tables: [] } if not found; { tables: [name, ...] } if found. Never hal
     inputSchema: z.object({
       name: z.string(),
       lib: z.string(),
-      server: z.string().optional() // default server is 'cas'
+      server: z.string() 
     }),
     
     handler: async (params) => {