Skip to main content
Glama
Sign In
SAS MCP Server

SAS MCP Server

Official
by sassoftware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Update Value List Entries

update_value_list_entries
DestructiveIdempotent

Replace all entries in a value list's newest version while preserving the production version; the update creates a new version with the supplied entries.

Instructions

Replace the entries of a value list's newest version.

A version already in production is left alone: a new version holds the entries instead.

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": {
      "value_list_id": "<value_list_id>",
      "entries": "<entries>"
    },
    "name": "update_value_list_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
entriesYesThe complete new entries, as strings or ``{"key", "label"}`` objects.
value_list_idYesThe value list ID.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.19.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true. The description adds genuinely useful behavior beyond that: the production version is preserved and a new version is created instead, which substantially changes how an agent should reason about the destructive flag. It stops short of saying whether the new version needs publishing before taking effect.

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?

Two short sentences, front-loaded with the action and followed by the one piece of non-obvious behavior. Nothing is wasted and nothing important is buried.

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?

With a full schema and an output schema present, the description covers the main thing an agent cannot infer: the versioning side effect. It could still clarify whether the new version is live immediately or requires a publish step, but overall it is complete enough to call the tool correctly.

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%, with both parameters documented, including the accepted string-or-{key,label} entry format. The description adds no parameter detail beyond the schema, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource: 'Replace the entries of a value list's newest version.' This clearly separates it from create_value_list or update_lookup_table, but it doesn't name any sibling explicitly. The scope (newest version only) is precise.

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?

Usage is implied by the versioning rule: use this to change entries, and the tool handles version creation for you. There is no explicit when-to-use versus when-to-use-something-else guidance and no named alternative among the many sibling tools.

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