Skip to main content
Glama
sassoftware

SAS MCP Server

Official
by sassoftware

Get Decisioning Asset

get_decisioning_asset
Read-onlyIdempotent

Fetch decisioning content such as rule sets, code files, value lists, or lookup tables—or a specific revision—with folder context, and summarize oversized assets.

Instructions

Fetch one piece of decisioning content, or one of its revisions, with the folder it is in.

A rule set comes with its rules, a code file with its code, a value list with the entries of its newest version, a lookup table with its versions, the entries of its active one (get_lookup_table pages and filters them) and the rule sets that use it. Content larger than 150,000 characters — a big segmentation tree — is summarised (counts, root variable) instead of returned whole; summary_only asks for the summary of anything.

Input Schema

NameRequiredDescriptionDefault
asset_idYesThe ID (not the name — list_decisioning_assets returns both); a lookup table may also be given by its exact name.
asset_typeYesrule_set, decision, segmentation_tree, code_file, value_list, lookup_table, custom_function or function_category.
revision_idNoA revision to read instead of the current state (for a lookup table: a version ID or label).
summary_onlyNoReturn the summary rather than the full content.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.19.0

TDQS

A4.5/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: it explains per-asset-type return shapes, revision handling, automatic summarization above 150,000 characters, and the summary_only option. These are important operational details for an agent invoking the tool.

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 front-loaded with the core action, then uses compact sentences to cover per-type returns and the large-content summarization rule. Every sentence provides useful information without redundant 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?

With annotations covering safety and idempotency, a full output schema, and complete parameter descriptions, the description supplies the remaining critical context: per-type return behavior, revision semantics, and summarization limits. Nothing material appears missing for correct invocation.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents asset_id, asset_type, revision_id, and summary_only. The description adds useful context about how asset_type affects returned content and how revision_id / summary_only behave, but it does not need to compensate for schema gaps.

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: fetch one decisioning asset or revision, including its folder. It further clarifies what is returned for each asset type, which makes the tool distinguishable from siblings such as get_lookup_table and list_decisioning_assets.

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?

Usage is clear from the opening sentence and the parenthetical note that get_lookup_table pages and filters lookup table entries, which is an explicit alternative for that asset type. It does not explicitly cover when to use this versus get_decisioning_asset_code or list_decisioning_asset_revisions, 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