Skip to main content
Glama

ADS Beast

get_prepared_change

Read-only

What became of a preview: still ready, expired, or submitted - and then the proposal's status (pending, executed, rejected, failed) with the execution result.

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": {
      "preview_id": "<preview_id>"
    },
    "name": "get_prepared_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
preview_idYesThe preview_id returned by a prepare_* tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a read-only, non-destructive, open-world operation, so the safety profile is covered. The description goes beyond that by disclosing the full set of possible states the caller can receive, which is the key behavioral fact for a status tool. It does not explain whether expired previews can be re-prepared or how long readiness persists.

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

Conciseness4/5

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

It is a single compact sentence with the key information front-loaded. The phrasing 'and then the proposal's status' is slightly loose, but no sentence is wasted.

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 no output schema, the description carries the return-value burden and does so reasonably by enumerating the preview states and proposal statuses, plus mention of an execution result. It leaves the shape of that execution result and any timing semantics unstated, which is the main remaining gap.

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 coverage is 100% and the single preview_id parameter is fully documented as coming from a prepare_* tool. The description adds nothing about the identifier beyond what the schema states, so the baseline of 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?

The description names the resource and the action precisely: it reports what became of a preview and the resulting proposal status. The enumerated states ('ready, expired, submitted' then 'pending, executed, rejected, failed') make the tool's domain unmistakable. It stops short of explicitly contrasting itself with execute_prepared_change, which is the natural sibling.

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 only implied: the mention of a preview and 'submitted' status suggests polling after a prepare_* tool and possibly after execution. There is no explicit statement of when to call this versus execute_prepared_change, and no guidance on re-polling or when the status is final.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.