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

package/skills/sas-score-workflow/SKILL.md

@@ -1,4 +1,4 @@
----
+gi ---
 name: sas-score-workflow
 description: >
   Guide the full model scoring workflow: validate model familiarity, route to appropriate scoring tool 
@@ -25,11 +25,11 @@ score <name>.<type> [scenario =<key=value pairs>]
 ```
 
 **Type determines the routing:**
-- `.job` → route to `run-job` with scoring parameters
-- `.jobdef` → route to `run-jobdef` with scoring parameters
-- `.mas` → route to `model-score` (Model Analytical Service — default)
-- `.scr` → route to `scr-score` (SAS Container Runtime)
-- `.sas` → route to `run-sas-program` to run sas program in folder
+- `.job` → route to `sas-score-run-job` with scoring parameters
+- `.jobdef` → route to `sas-score-run-jobdef` with scoring parameters
+- `.mas` → route to `sas-score-model-score` (Model Analytical Service — default)
+- `.scr` → route to `sas-score-scr-score` (SAS Container Runtime)
+- `.sas` → route to `sas-score-run-sas-program` to run sas program in folder
 
 If no type is specified (bare model name), assume `.mas` (MAS model).
 
@@ -51,39 +51,39 @@ When a user provides a model name with a type suffix (e.g., `simplejon.job`, `ch
 
 3. **Strip the type suffix:** Remove the `.type` from the model name before passing to the routing tool
    - **Critical:** Always pass the base name (without the dot and type) to the invoked tool
-   - `simplejon.job` → pass `simplejon` to `run-job`
-   - `churn.mas` → pass `churn` to `model-score`
-   - `fraud_detector.jobdef` → pass `fraud_detector` to `run-jobdef`
+   - `simplejon.job` → pass `simplejon` to `sas-score-run-job`
+   - `churn.mas` → pass `churn` to `sas-score-model-score`
+   - `fraud_detector.jobdef` → pass `fraud_detector` to `sas-score-run-jobdef`
 
 ### Type: `.mas` (Model Aggregation Service)
-- **Tool**: `model-score`
+- **Tool**: `sas-score-model-score`
 - **Use for**: Standard MAS-deployed predictive models
 - **Example**: `score with model churn.mas scenario =age=45,income=60000`
-- **Invocation**: `model-score({ model: "churn", scenario: {...} })`
+- **Invocation**: `sas-score-model-score({ model: "churn", scenario: {...} })`
 
 ### Type: `.job` (SAS Viya Job)
-- **Tool**: `run-job`
+- **Tool**: `sas-score-run-job`
 - **Use for**: Pre-built scoring jobs with parameters
 - **Example**: `score with model monthly_scorer.job scenario =month=10,year=2025`
-- **Invocation**: `run-job({ name: "monthly_scorer", scenario: {...} })`
+- **Invocation**: `sas-score-run-job({ name: "monthly_scorer", scenario: {...} })`
 
 ### Type: `.jobdef` (SAS Viya Job Definition)
-- **Tool**: `run-jobdef`
+- **Tool**: `sas-score-run-jobdef`
 - **Use for**: Job definitions that perform scoring logic
 - **Example**: `score with model fraud_detector.jobdef using amount=500,merchant=online`
-- **Invocation**: `run-jobdef({ name: "fraud_detector", scenario: {...} })`
+- **Invocation**: `sas-score-run-jobdef({ name: "fraud_detector", scenario: {...} })`
 
 ### Type: `.scr` (Score Code Runtime)
-- **Tool**: `scr-score`
+- **Tool**: `sas-score-scr-score`
 - **Use for**: Models deployed in SCR containers (REST endpoints)
 - **Example**: `score https://scr-host/models/loan.scr using age=45,credit=700`
-- **Invocation**: `scr-score({ url: "https://scr-host/models/loan", scenario: {...} })`
+- **Invocation**: `sas-score-scr-score({ url: "https://scr-host/models/loan", scenario: {...} })`
 
 ### Type: `.sas` (SAS Program / SQL)
-- **Tool**: `run-sas-program`
+- **Tool**: `sas-score-run-sas-program`
 - **Use for**: Custom SAS or SQL scoring code
 - **Example**: `score my_scoring_code.sas using x=1,y=2`
-- **Invocation**: `run-sas-program({ folder: "my_scoring_code", scenario: {...} })`
+- **Invocation**: `sas-score-run-sas-program({ folder: "my_scoring_code", scenario: {...} })`
 
 
 
@@ -106,6 +106,13 @@ Accepted formats:
 
 ---
 
+## Integration with other skills
+
+- **Before scoring table data**: Use `sas-find-library-smart` to verify the library, then `sas-read-strategy` to fetch records
+- **For read + score workflows**: Use `sas-read-and-score` for the complete end-to-end pattern
+
+---
+
 ## Step 1 — Check model familiarity before scoring
 
 Score immediately if:
@@ -139,7 +146,7 @@ scenario = [
 ```
 
 **Critical rules:**
-- Loop or call model-score **once per row**.
+- Loop or call sas-score-model-score **once per row**.
 - Field names in the scenario must match the model's expected input variable names **exactly**.
   - If table column names differ from model input names, **flag this to the user** and ask for confirmation before scoring.
   - Example: Table has `age_years`, but model expects `age` → ask user which column maps to which input.
@@ -153,7 +160,7 @@ Based on the type extracted from the model name, invoke the corresponding tool:
 
 **For `.mas` (default):**
 ```javascript
-model-score({
+sas-score-model-score({
   model: "<modelname>",
   scenario: scenario,  // object or array
   uflag: false         // set true if you need field names prefixed with _
@@ -162,7 +169,7 @@ model-score({
 
 **For `.job`:**
 ```javascript
-run-job({
+sas-score-run-job({
   name: "<jobname>",
   scenario: scenario
 })
@@ -170,7 +177,7 @@ run-job({
 
 **For `.jobdef`:**
 ```javascript
-run-jobdef({
+sas-score-run-jobdef({
   name: "<jobdefname>",
   scenario: scenario
 })
@@ -178,7 +185,7 @@ run-jobdef({
 
 **For `.scr`:**
 ```javascript
-scr-score({
+sas-score-scr-score({
   url: "<scr_endpoint_url>",
   scenario: scenario
 })
@@ -186,7 +193,7 @@ scr-score({
 
 **For `.sas`:**
 ```javascript
-run-sas-program({
+sas-score-run-sas-program({
   src: "<sas_or_sql_code>",
   scenario: scenario
 })
@@ -222,43 +229,43 @@ Merge the scoring output back with the input records and present as a table wher
 **Flow A — Score rows with MAS model**
 > "Score the first 10 customers in Public.customers with the churn model"
 
-1. `read-table` → { table: "Public.customers", limit: 10 }
-2. `model-score` → { model: "churn", scenario: [ ...10 row objects ] }
+1. `sas-score-read-table` → { table: "Public.customers", limit: 10 }
+2. `sas-score-model-score` → { model: "churn", scenario: [ ...10 row objects ] }
 3. Present merged results with prediction + key inputs
 
 **Flow B — Score with a scoring job**
 > "Score December sales with the monthly_scorer job using month=12,year=2025"
 
-1. `run-job` → { name: "monthly_scorer", scenario: { month: "12", year: "2025" } }
+1. `sas-score-run-job` → { name: "monthly_scorer", scenario: { month: "12", year: "2025" } }
 2. Capture job output and tables
 3. Present results
 
 **Flow C — Score with a job definition**
 > "Run fraud detection jobdef on transaction amount=500, merchant=online"
 
-1. `run-jobdef` → { name: "fraud_detection", scenario: { amount: "500", merchant: "online" } }
+1. `sas-score-run-jobdef` → { name: "fraud_detection", scenario: { amount: "500", merchant: "online" } }
 2. Capture log, listings, and tables
 3. Present results
 
 **Flow D — Score with SCR endpoint**
 > "Score with the loan model at https://scr-host/models/loan using age=45, credit_score=700"
 
-1. `scr-score` → { url: "https://scr-host/models/loan", scenario: { age: "45", credit_score: "700" } }
+1. `sas-score-scr-score` → { url: "https://scr-host/models/loan", scenario: { age: "45", credit_score: "700" } }
 2. Capture prediction response
 3. Present result
 
 **Flow E — Score results of an analytical query with MAS**
 > "Score high-value customers (spend > 5000) in mylib.sales with the fraud model"
 
-1. `sas-query` → { table: "mylib.sales", sql: "SELECT * FROM mylib.sales WHERE spend > 5000" }
-2. `model-score` → { model: "fraud", scenario: [ ...result rows ] }
+1. `sas-score-sas-query` → { table: "mylib.sales", sql: "SELECT * FROM mylib.sales WHERE spend > 5000" }
+2. `sas-score-model-score` → { model: "fraud", scenario: [ ...result rows ] }
 3. Present merged results
 
 **Flow F — User supplies scenario data directly**
 > "Score age=45, income=60000, region=South with the churn model"
 
 1. Skip read step
-2. `model-score` → { model: "churn", scenario: { age: "45", income: "60000", region: "South" } }
+2. `sas-score-model-score` → { model: "churn", scenario: { age: "45", income: "60000", region: "South" } }
 3. Present result
 
 **Flow G — Model unfamiliar, need to confirm**
@@ -266,7 +273,7 @@ Merge the scoring output back with the input records and present as a table wher
 
 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`
+3. Once confirmed → `sas-score-read-table` + `sas-score-model-score`
 
 **Flow H — Generic score syntax with type routing**
 > "score with model churn.mas scenario =age=45,income=60000"
@@ -294,7 +301,14 @@ Merge the scoring output back with the input records and present as a table wher
 
 ## Tips
 
-- **Batch is better:** Always pass the full set of records in one `model-score` call. Do not loop.
+- **Batch is better:** Always pass the full set of records in one `sas-score-model-score` call. Do not loop.
 - **Confirm mappings:** If column names don't match model inputs, ask before scoring.
 - **Show context:** Include key input columns in the result output so predictions make sense.
 - **Limit output:** For large result sets (>10 rows), ask before showing all.
+
+---
+
+## Integration with other skills
+
+- **Before scoring table data**: Use `sas-find-library-smart` to verify the library, then `sas-read-strategy` to fetch records
+- **For read + score workflows**: Use `sas-read-and-score` for the complete end-to-end pattern

package/src/oauthHandlers/callback.js

@@ -31,15 +31,18 @@ async function callback(req, res, pkceStore, codeStore, appContext) {
     }).toString();
    
     console.error("[Note] Token request body:", body.toString());
+  
     let connectOpts = {
-      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) {
+      connectOpts.ca = appContext.contexts.viyaCert.ca;
+    }
     const agent = new Agent({ connect: connectOpts });
     console.error("[Note] Initiating token exchange with SAS Viya");
     let clientID= appContext.CLIENTID;
     let h = buildBasicAuthFromClientId(clientID);
-    console.error("[Note] Authorization header for token request:", h);
+    // console.error("[Note] Authorization header for token request:", h);
     const response = await undiciFetch(`${appContext.VIYA_SERVER}/SASLogon/oauth/token`, {
       method: "POST",
       headers: {
@@ -57,7 +60,7 @@ async function callback(req, res, pkceStore, codeStore, appContext) {
     }
 
     const tokens = await response.json();
-    console.error("[Note] Received tokens from SAS Viya:", tokens);
+   // console.error("[Note] Received tokens from SAS Viya:", tokens);
     const ourCode = randomUUID();
     codeStore.set(ourCode, {
       access_token: tokens.access_token,

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);