Skip to main content
Glama
Sign In
SAS MCP Server

SAS MCP Server

Official
by sassoftware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Create Business Ruleset

create_business_ruleset

Creates a SAS Business Rules rule set in a specified or default folder, defining input and output variables so you can add rules for use in decision flows.

Instructions

Create a new SAS Business Rules rule set in a SAS Content folder.

A rule set with no rules cannot be used in a decision flow — follow up with create_business_rule to populate it.

The rule set is always stored in a folder. Without folder it goes to the deployment's default folder; when there is none, the call is refused and you should ask the user which folder to use. The result's folder says where it was stored.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "signature": "<signature>"
    },
    "name": "create_business_ruleset"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRule set name (max 30 chars).
folderNoWhere to store the rule set: a folder path such as ``/Public/Content/Decisions``, ``My Folder`` (or a folder below it, ``My Folder/Risk``), a folder ID, or a folder URI (``/folders/folders/<id>``). Omit to use the default folder.
signatureYesInput/output/inOut variables the rules operate on, each ``{"name", "dataType", "direction"}`` — dataType one of string, decimal, integer, date, datetime, dataGrid, boolean, any; direction one of input, output, inOut.
descriptionNoOptional description.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.19.0
    • addedInput schema / properties / folder
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Where to store the rule set: a folder path such as\n``/Public/Content/Decisions``, ``My Folder`` (or a folder below\nit, ``My Folder/Risk``), a folder ID, or a folder URI\n(``/folders/folders/<id>``). Omit to use the default folder."
+}
  2. Addedv1.5.0

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond annotations declaring a non-read-only, non-destructive create operation, the description discloses key behavior: the rule set is always folder-scoped, omitted folder uses a deployment default, no default causes refusal, and the result reports the storage folder. This gives the agent important operational context and error handling guidance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded: the create action comes first, followed by the required follow-up, then folder-storage edge cases. Every sentence carries actionable information without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema and annotations, the description supplies the remaining context an agent needs: dependency on create_business_rule, folder fallback behavior, refusal handling, and result folder reporting. Parameter-level details such as name length and signature structure are adequately covered by the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all four parameters in detail. The description adds meaningful semantics for the folder parameter by explaining default behavior and refusal conditions when folder is omitted, though it does not add equivalent detail for signature beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Create a new SAS Business Rules rule set in a SAS Content folder.' It also distinguishes rule-set creation from rule creation by instructing the agent to follow up with create_business_rule to populate the set.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear workflow guidance: an empty rule set cannot be used in a decision flow, so create_business_rule should follow. It also explains folder omission behavior and when the call is refused. It does not explicitly compare against update/get/list siblings, so it falls short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools