Skip to main content
Glama
Sauerbraten MCP
by pastukhov

history_redo

Redoes the last shared manual or MCP history step and returns the updated state, allowing recovery of an undone level edit.

Instructions

Redo the top shared manual/MCP history step; read state afterwards.

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>",
      "map_epoch": "<map_epoch>",
      "expected_revision": "<expected_revision>"
    },
    "name": "history_redo"
  }
}

Input Schema

NameRequiredDescriptionDefault
map_epochYes
request_idYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

The annotations already declare this is a non-read-only, non-destructive, non-idempotent mutation, so the description does not need to restate the safety profile. 'Read state afterwards' is genuinely useful added context, telling the agent the tool's result must be followed by a state read. However, the description omits key behavioral facts the annotations do not cover: the required expected_revision implies optimistic-concurrency failure modes, and neither redo-stack exhaustion nor error behavior is mentioned.

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?

A single short sentence with the operation front-loaded and no filler; both clauses carry information. The only weakness is that 'manual/MCP' and 'shared' are undefined jargon that a reader outside this system cannot resolve from the text alone.

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

Completeness2/5

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

This is a mutation tool with three required, entirely undocumented parameters and no output schema. The description never explains the optimistic-concurrency contract implied by expected_revision, what state the caller should read afterwards, or failure cases. For a versioned write operation, that leaves an agent without enough information to invoke it safely.

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

Parameters1/5

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

Schema description coverage is 0%, and all three parameters (request_id, map_epoch, expected_revision) are required but have only titles and regex patterns. The description supplies no meaning at all for them — it does not say what request_id is for, what map_epoch scopes, or that expected_revision is a version guard that can cause a conflict rejection. With the schema carrying zero semantic content, the description must compensate and does not.

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 ('Redo') and a specific resource ('the top shared manual/MCP history step'), which pins down both the operation and its scope to a single step. The sibling history_undo is implicitly the inverse, though the description never names it or clarifies what 'manual/MCP' covers. A capable agent can tell what this does without opening the schema.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no reference to history_undo as the alternative, even though the sibling list makes that the obvious counterpart. 'Top step' implies it only makes sense when a redo stack is non-empty, but the description never says what happens when there is nothing to redo. Guidance is inferred rather than stated.

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