Skip to main content
Glama
Sauerbraten MCP
by pastukhov

operation_status

Read-onlyIdempotent

Check a mutation request's status by UUID to verify whether a prior edit succeeded and avoid blindly repeating it.

Instructions

Look up a mutation UUID; unknown means do not blindly repeat it.

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": {
      "request_id": "<request_id>"
    },
    "name": "operation_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered structurally. The description adds genuine context beyond that: the concept of an 'unknown' outcome and the warning against blindly re-issuing the mutation, which is the key decision an agent makes after a status check. It does not explain what status values or ambiguity conditions exist, hence not a 5.

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?

One compact sentence with the action first and the retry caveat attached; nothing is padded. The tradeoff is that 'unknown' is undefined, making the phrase slightly cryptic, but it is appropriately sized.

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

Completeness3/5

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

There is no output schema, so the description carries the burden of explaining what a lookup returns, yet it never enumerates statuses or clarifies what 'unknown' means in practice. For a low-complexity, single-parameter read tool this is workable but leaves the central interpretation question open.

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 0% — the schema only labels the field 'Request Id' with a UUID regex. The description supplies the crucial meaning that this is a mutation UUID, telling the agent which identifier to supply. Given a single parameter with no documented semantics in the schema, this compensates well.

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

Purpose3/5

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

The verb 'look up' plus 'mutation UUID' suggests retrieving the status of a prior mutation, but the phrasing 'look up a mutation UUID' is ambiguous about whether the UUID is the input or the output. It never states what is returned, so an agent must infer that this is a status check rather than a fetch of the identifier itself.

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?

It gives one conditional behavior: when the result is unknown, do not blindly repeat the mutation. That is real usage guidance for a retry decision, but it offers no positive 'use this when' framing or naming of alternatives (e.g., retrying via the mutation tool itself).

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