@sassoftware/sas-score-mcp-serverjs 1.0.1-2 → 1.0.1-3

package/.skills_github/copilot-instructions.md

@@ -0,0 +1,177 @@
+# SAS Agent instructions for this repository
+
+## Project overview
+This repository builds and maintains a SAS-focused agent experience on top of an MCP server.
+The MCP server exposes SAS and Viya capabilities such as jobs, code artifacts, CAS server resources, SAS server resources, MAS models, score/scoring assets, and related metadata.
+Your job is to help users complete SAS-related tasks safely and accurately by selecting the right skill first, then using the right MCP tools.
+
+## Available Agents
+
+This repository includes specialized agents for SAS-focused workflows:
+
+- **SAS Viya Scoring Expert** — Specialized for SAS Viya scoring tasks. Classifies requests, selects the right SAS skill, and uses MCP tools safely for jobs, CAS data, libraries, models, scoring, and content workflows.
+- **Explore** — General codebase exploration and Q&A agent. Use for discovering code patterns, reading documentation, or quick exploratory questions.
+
+You can invoke these agents using the subagent feature. Type `/subagent` followed by your request or choose an agent from the dropdown when available.
+
+## Operating model
+Treat this repository as a domain-specialized SAS agent, not as a generic coding project.
+Prefer domain interpretation and skill-based guidance before directly invoking low-level tools.
+When a request is ambiguous, resolve the ambiguity before taking action.
+
+## Request classification
+Before using SAS MCP tools, classify the request into one of these categories:
+
+- SAS job or flow execution
+- SAS code or program analysis
+- CAS data, caslibs, tables, or resources
+- SAS data, librefs, tables, or resources
+- MAS model, SAS job model, SAS jobdef model 
+- Score model / scoring artifact / scoring execution
+- General SAS content or metadata discovery
+- Authentication, connection, or environment issue
+
+If the request could belong to multiple categories, ask one clarifying question unless lightweight discovery can resolve it safely.
+
+## Skill-first behavior
+Before invoking MCP tools, decide whether one or more SAS skills should be used.
+Prefer loading the most relevant SAS skill for the request category.
+Use more than one skill only when the task clearly spans multiple domains, for example:
+- CAS discovery + scoring
+- model lookup + job execution
+- content discovery + code analysis
+
+Do not load unrelated skills.
+Do not treat "model", "score", "job", "code", or "table" as interchangeable terms.
+
+## Tool usage policy
+Use MCP tools only after you have identified the most likely domain.
+Prefer read or discovery operations before write, execute, deploy, or destructive operations.
+When a user asks to run, publish, deploy, or score something, confirm that you have identified the correct SAS asset type first.
+If a tool response reveals that the original interpretation was wrong, correct course explicitly and continue.
+
+## Ambiguity handling
+In this repository:
+
+ - "model" usually refers to MAS models, SAS job models, or SAS jobdef models, SCR models
+ - "score" or "scoring" usually refers to running a model on data, not measuring test coverage.
+ - "job"  usually refers to a SAS job or flow, not a CI job.
+
+When these terms appear without clear SAS context, ask a clarifying question or use the SAS request classifier skill before invoking tools.
+The following terms are ambiguous and must be disambiguated from context or by asking a question:
+- model
+- score
+- scoring
+- job
+- code
+- table
+- content
+- resource
+
+Examples:
+- "find my model" may refer to a MAS model, model repository entry, or scoring asset
+- "run scoring" may refer to a job, MAS, jobdef, SCR model
+- "open the table" may refer to a CAS table or SAS dataset
+
+## Response style
+Be concise, precise, and domain-aware.
+Explain which SAS concept you are acting on when ambiguity is possible.
+Do not pretend certainty when the asset type or environment is unclear.
+Prefer structured answers with short steps when guiding the user.
+
+## Coding and implementation guidance
+When editing code in this repository:
+- Preserve existing MCP server patterns and naming conventions.
+- Prefer small, composable modules over large prompt files.
+- Keep tool descriptions short, specific, and distinct.
+- Put durable domain workflows in skills, not in tool descriptions.
+- Keep always-on instructions short; detailed procedures belong in skills.
+- Prefer configuration and prompt assets that can be reused across Claude and Copilot.
+
+## Repository structure expectations
+Expect to find:
+- MCP server implementation code
+- prompt or skill assets
+- configuration for client integrations
+- SAS/Viya-specific adapters or resource logic
+- tests or examples for skill and tool behavior
+
+When adding new artifacts:
+- Put repo-wide guidance in `.github/copilot-instructions.md`
+- Put targeted reusable workflows in `.github/skills/<skill-name>/SKILL.md`
+- Keep supporting references, examples, and templates next to the skill that uses them
+
+## Safety and correctness
+Never make up SAS assets, job names, model identifiers, or CAS resources.
+If a requested action depends on environment-specific details, verify those details first.
+Prefer inspection and discovery over assumption.
+
+---
+
+# Available Skills
+
+This repository provides specialized skills for SAS-focused workflows. Load the relevant skill for the user's request before using MCP tools.
+
+## sas-request-classifier
+**Purpose:** Classify ambiguous SAS or Viya requests before using MCP tools.
+
+**Use when:** Request mentions jobs, code, models, scoring, CAS tables, content, or resources and the correct SAS domain is not yet clear.
+
+**Trigger phrases:** "find my model", "run scoring", "open the table", or any ambiguous request using domain terms.
+
+## sas-find-resource-strategy
+**Purpose:** Unified find-only strategy to verify existence of libraries, tables, models, jobs, and jobdefs using find tools.
+
+**Use when:** User asks to find, verify, check existence of, or locate a resource.
+
+**Trigger phrases:** "find library", "find table", "find model", "find job", "find jobdef", "does X exist".
+
+## sas-list-resource-strategy
+**Purpose:** Unified list strategy to list libraries, tables, models, jobs, and jobdefs with normalized pagination.
+
+**Use when:** User asks to list, show, browse, or enumerate resources.
+
+**Rule:** Always pass non-null `start` and `limit`; default to `start: 1` and `limit: 10` when not provided.
+
+**Trigger phrases:** "list libraries", "list tables", "list models", "list jobs", "list jobdefs", "show resources".
+
+## sas-find-library-smart
+**Purpose:** Find a SAS Viya library (libref or caslib) with intelligent server detection. Automatically checks CAS first, then SAS if not found.
+
+**Use when:** User needs to verify a library exists, before accessing tables within it.
+
+**Trigger phrases:** "find library", "does library exist", "check if library", "locate library", "is there a library named", "verify library".
+
+## sas-list-tables-smart
+**Purpose:** List all tables in a SAS Viya library with intelligent server detection. When the server is not specified, automatically checks CAS first, then SAS if not found.
+
+**Use when:** User wants to browse or explore available tables.
+
+**Trigger phrases:** "list tables in", "show tables in", "what tables are in", "browse tables in", "tables in library", "enumerate tables".
+
+## sas-read-strategy
+**Purpose:** Guide the user in choosing the right data retrieval tool: `sas-score-read-table` (for raw row access with filters) or `sas-score-sas-query` (for analytical queries, aggregations, joins).
+
+**Use when:** User wants to fetch records from a SAS/CAS table.
+
+**Pre-check:** Use `sas-find-resource-strategy` to verify library/table existence first.
+
+**Trigger phrases:** "read records from", "get data where", "fetch rows from", "query the table", "give me the first N records", "aggregate by", "join tables".
+
+## sas-read-and-score
+**Purpose:** Guide the full read → score workflow in SAS Viya: reading records from a table and then scoring them with a MAS model.
+
+**Use when:** 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.
+
+**Pre-check:** Use `sas-find-resource-strategy` to verify library/table/model resources first.
+
+**Trigger phrases:** "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".
+
+## sas-score-workflow
+**Purpose:** Mandatory routing logic for all scoring requests. Extracts model.type suffix and routes to the correct tool (run-job|run-jobdef|model-score|scr-score|run-program). Handles both MAS models and alternative scoring engines.
+
+**Use when:** User requests scoring with a model name that may require routing to different execution engines.
+
+**Pre-check:** Use `sas-find-resource-strategy` to verify model/job/jobdef resources before execution.
+
+**Trigger phrases:** "score with model X.job", "score X.jobdef scenario", "score with model X.mas", "score with model X.scr", any request with "score" + model name containing a dot (.) + type suffix.

package/.skills_github/skills/sas-find-library-smart/SKILL.md

@@ -0,0 +1,155 @@
+---
+name: sas-find-library-smart
+description: >
+  Find a SAS Viya library (libref or caslib) with intelligent server detection. Automatically checks 
+  CAS first, then SAS if not found. Use this skill when the user needs to verify a library exists,
+  before accessing tables within it. Trigger phrases include: "find library", "does library exist",
+  "check if library", "locate library", "is there a library named", "verify library", or any request 
+  to confirm a library's availability across servers.
+---
+
+# Smart Library Lookup (Find Library)
+
+Intelligently locates a SAS Viya library by checking CAS first, then SAS if the library is not found 
+in CAS. Provides the user with clear information about library availability and location.
+
+> Primary strategy: use `sas-find-resource-strategy` for all resource existence checks.
+
+**If the user specifies the server explicitly** (e.g., "find library Public in cas"):
+- Use the specified server: `server: "cas"` or `server: "sas"`
+- Proceed directly to finding the library
+
+**If the server is NOT specified:**
+1. **First attempt**: Check CAS (`server: "cas"`)
+2. **If not found in CAS**: Check SAS with uppercase library name (`server: "sas"`)
+3. **If not found in either**:
+   - Inform user: *"The library '<lib>' was not found in CAS or SAS servers. Please verify the library name."*
+  - Ask for corrected library name or explicit server context
+4. **If found**:
+   - Inform user which server contains the library: *"Found library '<lib>' in CAS"* or *"Found library '<lib>' in SAS"*
+   - Offer next steps: *"Would you like to list tables in this library?"* (suggest `sas-score-list-tables`)
+
+---
+
+## Using sas-score-find-library
+
+**When:**
+- User wants to verify a library exists
+- User needs to determine which server contains a library
+- User wants to check library availability before accessing it
+- User wants to explore available libraries (before querying)
+
+**How:**
+```
+sas-score-find-library({
+  name: "libraryname",          // required
+  server: "cas" or "sas"        // optional; determined by server check if not specified
+})
+```
+
+**Rules:**
+- Always determine the correct server first (cas → sas → neither)
+- **For SAS server: always uppercase the library name** (e.g., "public" → "PUBLIC")
+- If library name is missing, ask: *"Which library name would you like to find?"*
+- Return the server where the library was found
+- If not found in either server, clearly inform the user and request corrected name or server context
+- Do not proceed with table access until library existence is confirmed
+- Do not use list tools to find whether a library exists
+
+---
+
+## Smart server detection logic
+
+```
+IF server specified by user
+  → IF server is "sas"
+      → uppercase lib
+  → use that server, call sas-score-find-library
+ELSE
+  → TRY sas-score-find-library(lib, server="cas")
+    IF library found
+      → success, inform user: library found in CAS
+    ELSE
+      → uppercase lib
+      → TRY sas-score-find-library(lib.toUpperCase(), server="sas")
+        IF library found
+          → success, inform user: library found in SAS
+        ELSE
+          → inform user library not found in either server
+          → ask for corrected name or explicit server
+```
+
+---
+
+## Common patterns
+
+**Pattern 1 — Find library, server unspecified**
+> "Find library Public"
+
+1. Try CAS: `sas-score-find-library({ name: "Public", server: "cas" })`
+2. If not found, try SAS with uppercase: `sas-score-find-library({ name: "PUBLIC", server: "sas" })`
+3. If found in CAS → *"Found library 'Public' in CAS. Would you like to list tables in it?"*
+4. If found in SAS → *"Found library 'PUBLIC' in SAS. Would you like to list tables in it?"*
+5. If not found -> *"The library 'Public' was not found in CAS or SAS. Please confirm the name or specify a server."*
+
+**Pattern 2 — Find library with explicit server (CAS)**
+> "Find library MyData in cas"
+
+1. Skip server detection
+2. Call: `sas-score-find-library({ name: "MyData", server: "cas" })`
+3. Result → *"Found library 'MyData' in CAS"* or *"Library 'MyData' not found in CAS"*
+
+**Pattern 3 — Find library with explicit server (SAS)**
+> "Does library SASHELP exist in sas"
+
+1. Skip server detection
+2. Uppercase lib: `sas-score-find-library({ name: "SASHELP", server: "sas" })`
+3. Result → *"Found library 'SASHELP' in SAS"* or *"Library 'SASHELP' not found in SAS"*
+
+**Pattern 4 — Library not found, offer next steps**
+> "Check if library staging exists"
+
+1. Try CAS: `sas-score-find-library({ name: "staging", server: "cas" })` → not found
+2. Try SAS: `sas-score-find-library({ name: "STAGING", server: "sas" })` → not found
+3. Respond:
+   - *"The library 'staging' was not found in CAS or SAS."*
+  - *"Please confirm the library name or specify the server (CAS or SAS)."*
+
+**Pattern 5 — Library found, follow-up action**
+> "Verify library samples exists"
+
+1. Try CAS: `sas-score-find-library({ name: "samples", server: "cas" })` → found
+2. Respond:
+   - *"Found library 'samples' in CAS."*
+   - *"Would you like to list tables in this library? (use `sas-score-list-tables`))"*
+
+---
+
+## Output presentation
+
+**When library is found:**
+```
+✓ Found library '<lib>' in <SERVER>
+
+Would you like to:
+• List tables in this library (use sas-list-tables-smart skill)
+• Read data from a specific table (use sas-read-strategy skill)
+```
+
+**When library is not found:**
+```
+✗ Library '<lib>' not found in either CAS or SAS
+
+Suggestions:
+• Check the spelling of the library name
+• Specify the intended server (CAS or SAS)
+• Try a different library name
+```
+
+---
+
+## Integration with other skills
+
+- **Primary find strategy**: Use `sas-find-resource-strategy` for existence checks
+- **After finding library → List tables**: Use `sas-list-tables-smart` skill to browse available tables
+- **After finding library → Read data**: Use `sas-read-strategy` skill to retrieve data from tables

package/.skills_github/skills/sas-find-resource-strategy/SKILL.md

@@ -0,0 +1,105 @@
+---
+name: sas-find-resource-strategy
+description: >
+  Unified strategy for finding SAS Viya resources using find tools only. Supports library, table,
+  model, job, and jobdef lookup with server-aware behavior for CAS/SAS resources. Use this skill
+  whenever the task is to verify whether a resource exists.
+---
+
+# SAS Find Resource Strategy
+
+Use this skill to verify resource existence without using list tools.
+
+## Scope
+
+Supported resource types:
+- library
+- table
+- model
+- job
+- jobdef
+
+## Mandatory rule
+
+- Use only find tools to verify existence.
+- Do not use list tools to find a resource.
+
+## Tool mapping
+
+- Library -> `sas-score-find-library`
+- Table -> `sas-score-find-table`
+- Model -> `sas-score-find-model`
+- Job -> `sas-score-find-job`
+- Jobdef -> `sas-score-find-jobdef`
+
+## Strategy by resource type
+
+### Find library
+
+If server is provided:
+- CAS: `sas-score-find-library({ name: "<lib>", server: "cas" })`
+- SAS: uppercase first, then `sas-score-find-library({ name: "<LIB>", server: "sas" })`
+
+If server is not provided:
+1. Check CAS first.
+2. If not found, check SAS with uppercase library name.
+3. Report where found, or report not found in either.
+
+### Find table
+
+Required inputs:
+- library name
+- table name
+
+If server is provided:
+- CAS: `sas-score-find-table({ lib: "<lib>", name: "<table>", server: "cas" })`
+- SAS: uppercase library first, then `sas-score-find-table({ lib: "<LIB>", name: "<table>", server: "sas" })`
+
+If server is not provided:
+1. Check CAS first.
+2. If not found, check SAS (uppercase library).
+3. If found in both, report both and ask user which server to use for follow-up reads.
+
+### Find model
+
+Use:
+- `sas-score-find-model({ name: "<model>" })`
+
+If a model type suffix is provided (for example `.mas`, `.job`, `.jobdef`, `.scr`):
+- For MAS model discovery, strip suffix and look up base name with `sas-score-find-model`.
+- For `.job` and `.jobdef`, use job and jobdef find tools instead of model find.
+
+### Find job
+
+Use:
+- `sas-score-find-job({ name: "<job>" })`
+
+### Find jobdef
+
+Use:
+- `sas-score-find-jobdef({ name: "<jobdef>" })`
+
+## Clarifying prompts
+
+Ask one focused question if required fields are missing:
+- Library missing for table lookup: "Which library contains the table?"
+- Table name missing: "Which table name should I check?"
+- Resource type ambiguous: "Do you want me to find a library, table, model, job, or jobdef?"
+
+## Output format
+
+For found resources:
+- Confirm exact resource name returned by the tool.
+- Confirm server when applicable (CAS/SAS).
+
+For not found resources:
+- State that the resource was not found.
+- Ask for corrected name or server context.
+
+## Examples
+
+- "find library Samples" -> CAS first, then SAS fallback using uppercase.
+- "find table costchange in Samples" -> CAS first, then SAS fallback using uppercase library.
+- "find model breastcancer" -> `sas-score-find-model`.
+- "find job simplejob" -> `sas-score-find-job`.
+- "find jobdef daily_run" -> `sas-score-find-jobdef`.

package/.skills_github/skills/sas-list-resource-strategy/SKILL.md

@@ -0,0 +1,124 @@
+---
+name: sas-list-resource-strategy
+description: >
+  Unified strategy for listing SAS Viya resources using list tools. Supports libraries,
+  tables, models, jobs, and jobdefs. Always normalize pagination so start and limit are
+  never null: default start=1 and limit=10 when not provided.
+---
+
+# SAS List Resource Strategy
+
+Use this skill to list resources with consistent pagination defaults.
+
+## Scope
+
+Supported resource types:
+- library
+- table
+- model
+- job
+- jobdef
+
+## Mandatory pagination rule
+
+For every list operation:
+- `start` must never be null
+- `limit` must never be null
+- If `start` is missing or null, set `start: 1`
+- If `limit` is missing or null, set `limit: 10`
+
+Normalization pattern:
+```
+start = (start == null) ? 1 : start
+limit = (limit == null) ? 10 : limit
+```
+
+## Tool mapping
+
+- Library -> `sas-score-list-libraries`
+- Table -> `sas-score-list-tables`
+- Model -> `sas-score-list-models`
+- Job -> `sas-score-list-jobs`
+- Jobdef -> `sas-score-list-jobdefs`
+
+## Strategy by resource type
+
+### List libraries
+
+Use:
+```
+sas-score-list-libraries({
+  server: "all" | "cas" | "sas",  // optional based on user intent
+  start: 1,
+  limit: 10
+})
+```
+
+If user provides server, honor it. If not, use default server behavior.
+
+### List tables
+
+Required input:
+- library name (`lib`)
+
+Use:
+```
+sas-score-list-tables({
+  lib: "libraryname",
+  server: "cas" | "sas",  // optional if strategy/tool supports detection
+  start: 1,
+  limit: 10
+})
+```
+
+If `lib` is missing, ask: "Which library should I list tables from?"
+
+### List models
+
+Use:
+```
+sas-score-list-models({
+  start: 1,
+  limit: 10
+})
+```
+
+### List jobs
+
+Use:
+```
+sas-score-list-jobs({
+  start: 1,
+  limit: 10
+})
+```
+
+### List jobdefs
+
+Use:
+```
+sas-score-list-jobdefs({
+  start: 1,
+  limit: 10
+})
+```
+
+## Clarifying prompts
+
+Ask one focused question if required context is missing:
+- Resource type unclear: "Do you want libraries, tables, models, jobs, or jobdefs?"
+- Listing tables without library: "Which library should I list tables from?"
+
+## Output and paging
+
+- Return the listed resources from the selected tool.
+- If result count equals `limit`, suggest next page with `start + limit`.
+- Keep using normalized pagination defaults unless user overrides.
+
+## Examples
+
+- "list jobs" -> `sas-score-list-jobs({ start: 1, limit: 10 })`
+- "list models" -> `sas-score-list-models({ start: 1, limit: 10 })`
+- "list jobdefs" -> `sas-score-list-jobdefs({ start: 1, limit: 10 })`
+- "list tables in Public" -> `sas-score-list-tables({ lib: "Public", start: 1, limit: 10 })`
+- "next jobs" after `{ start: 1, limit: 10 }` -> `sas-score-list-jobs({ start: 11, limit: 10 })`

package/.skills_github/skills/sas-list-tables-smart/SKILL.md

@@ -0,0 +1,128 @@
+---
+name: sas-list-tables-smart
+description: >
+  List all tables in a SAS Viya library with intelligent server detection. When the server is not
+  specified, automatically checks CAS first, then SAS if not found. Informs the user if the library
+  does not exist in either server. Use this skill when the user wants to browse or explore available
+  tables. Trigger phrases include: "list tables in", "show tables in", "what tables are in",
+  "browse tables in", "tables in library", "enumerate tables", or any request to explore data sources.
+---
+
+# Smart Data Access in SAS Library (List, Read, Query)
+
+Intelligently enumerates tables in a SAS Viya library, automatically determining the correct server
+when not explicitly specified.
+
+> **Pre-flight check**: Before listing tables, verify the library and table context using the `sas-find-resource-strategy` skill.
+> This ensures consistent server detection across all data operations.
+
+**If the user specifies the server explicitly** (e.g., "list tables in Public in cas"):
+- Use the specified server: `server: "cas"` or `server: "sas"`
+- Proceed directly to listing tables
+
+**If the server is NOT specified:**
+1. **First attempt**: Check CAS (`server: "cas"`)
+2. **If no tables found in CAS**: Check SAS (`server: "sas"`)
+3. **If no tables found in either**:
+   - Inform user: *"The library '<lib>' was not found in CAS or SAS. Please verify the library name is correct."*
+  - Ask for corrected library name or explicit server context
+
+---
+
+## Using sas-score-list-tables
+
+**When:**
+- User wants to browse all tables in a library
+- User wants to see what data is available
+- User wants to explore library contents before querying
+
+**How:**
+```
+sas-score-list-tables({
+  lib: "libraryname",           // required
+  server: "cas" or "sas",       // required; determined by server check
+  limit: 10,                    // optional; default 10, adjust for pagination
+  start: 1                      // optional; default 1, use for pagination
+})
+```
+
+**Rules:**
+- Always determine the correct server first (cas → sas → neither)
+- **For SAS server: always uppercase the library name** (e.g., "maps" → "MAPS")
+- If library name is missing, ask: *"Which library should I list tables from?"*
+- Default page size is 10; adjust based on user request ("show me all", "25 tables", etc.)
+- If returned table count equals the limit, suggest pagination: *"There may be more tables. Use `start: {next_offset}` to see more."*
+- If no tables are found despite library existing, report: *"No tables found in {lib} on {server} server."*
+- Return table names only; do not fetch table metadata unless explicitly requested
+- Do not use list tools to determine whether a specific resource exists
+
+---
+
+## Smart server detection logic
+
+```
+IF server specified by user
+  → IF server is "sas"
+      → uppercase lib
+  → use that server
+ELSE
+  → TRY sas-score-list-tables(lib, server="cas")
+    IF tables found
+      → success, return tables
+    ELSE
+      → uppercase lib
+      → TRY sas-score-list-tables(lib.toUpperCase(), server="sas")
+        IF tables found
+          → success, return tables
+        ELSE
+          → inform user library not found in either server
+```
+
+---
+
+## Common patterns
+
+**Pattern 1 — List tables, server unspecified**
+> "List tables in Public"
+
+1. Try CAS: `sas-score-list-tables({ lib: "Public", server: "cas" })`
+2. If empty, try SAS with uppercase: `sas-score-list-tables({ lib: "PUBLIC", server: "sas" })`
+3. If still empty → inform user
+
+**Pattern 2 — List tables with explicit server (SAS)**
+> "List tables in sashelp in sas"
+
+1. Skip server detection
+2. Call with uppercase lib: `sas-score-list-tables({ lib: "SASHELP", server: "sas" })`
+
+**Pattern 3 — List tables with explicit server (CAS)**
+> "List tables in Public in cas"
+
+1. No uppercase needed for CAS
+2. Call: `sas-score-list-tables({ lib: "Public", server: "cas" })`
+
+**Pattern 4 — Pagination**
+> "Show me 25 tables in Samples, then the next batch"
+
+1. First call: `sas-score-list-tables({ lib: "Samples", limit: 25, start: 1 })`
+2. Next call: `sas-score-list-tables({ lib: "Samples", limit: 25, start: 26 })`
+
+**Pattern 5 — Library not found**
+> "List tables in foo"
+
+1. Try CAS: empty
+2. Try SAS with uppercase: empty
+3. Response: *"The library 'foo' was not found in CAS or SAS. Please verify the library name."*
+
+---
+
+## Error handling
+
+| Scenario | Action |
+|---|---|
+| Library not found in either server | Inform user and ask to verify library name |
+| Empty result on first server | Automatically check second server |
+| User specifies invalid server | Return error; ask user to clarify: `"cas"` or `"sas"` |
+| Missing library name | Ask: *"Which library should I list tables from?"* |
+| Library verification needed | Use `sas-find-resource-strategy` to verify the library exists first |
+