Skip to main content
Glama
Sign In
SAS MCP Server

SAS MCP Server

Official
by sassoftware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Delete Decision Flow

delete_decision_flow
DestructiveIdempotent

Permanently delete a SAS Intelligent Decisioning flow by providing its decision flow UUID. Removes the specified flow to clean up decision logic.

Instructions

Permanently delete a SAS Intelligent Decisioning flow.

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": {
      "decision_id": "<decision_id>"
    },
    "name": "delete_decision_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
decision_idYesThe decision flow UUID to delete (not its name — list_decision_flows returns both).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.0
    • changedInput schema / properties / decision_id / description
      Previous value: -"The decision flow UUID to delete."New value: +"The decision flow UUID to delete (not its name — list_decision_flows returns both)."
  2. Addedv1.5.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description needs to add value beyond that. The word 'permanently' clarifies that deletion is irreversible rather than a soft delete or trash operation, and the parameter note '(not its name)' discloses that supplying a name will not work — both are genuine behavioral facts not present in the annotations.

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 a single eight-word sentence with the action front-loaded, and the parameter description packs three pieces of guidance into one compact sentence. There is no filler, repetition of schema details, or redundant phrasing.

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

Completeness4/5

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

For a single-parameter tool with full annotations (destructive, idempotent, read-only), an existing output schema, and a parameter description covering the main pitfall (UUID vs name), the definition is nearly complete. The only gap is unspecified cascade behavior, such as whether revisions or publish state affect deletion, which would be nice but is not essential at this complexity level.

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 description coverage is 100%, so the baseline is 3. The decision_id description goes beyond a simple field label by specifying the required format (UUID), stating a negative constraint (not its name), and naming the sibling tool that returns both identifiers. This materially helps an agent invoke the tool correctly on the first attempt.

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: 'Permanently delete a SAS Intelligent Decisioning flow.' The qualifier 'permanently' adds meaningful nuance beyond a generic delete, and the resource is precise enough to distinguish this from sibling deletes like delete_business_ruleset, delete_glossary_term, and delete_report.

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

Usage Guidelines3/5

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

The main description gives no explicit when-to-use or when-not-to-use direction. However, the decision_id parameter description supplies indirect usage guidance by clarifying that a UUID is required, not a name, and pointing to list_decision_flows as the discovery path. This covers the prerequisite but omits exclusions such as alternatives for reversible deletion or interaction with lock/publish states.

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