Skip to main content
Glama
Sauerbraten MCP
by pastukhov

history_undo

Reverts the most recent shared manual or MCP history step, then reads the resulting state.

Instructions

Undo 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_undo"
  }
}

Input Schema

NameRequiredDescriptionDefault
map_epochYes
request_idYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds real scope information (top step only, shared manual/MCP history) and a post-call behavior cue, but says nothing about no-op/failure cases or the meaning of the concurrency tokens it requires.

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 compact sentence with the scope constraint front-loaded and no filler; the "read state afterwards" clause is actionable rather than decorative. Its brevity borders on under-specification, but that is assessed in the other dimensions rather than penalized here.

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?

For a non-idempotent mutation with three undocumented required parameters and no output schema, one line is not enough. The description omits how revision/epoch guards work, what happens when there is nothing to undo, and what state the caller should read afterwards.

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

Parameters2/5

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

All three parameters (request_id, map_epoch, expected_revision) have 0% schema description coverage, so the description must carry their meaning and does not mention any of them. An agent gets no hint that map_epoch and expected_revision are optimistic-concurrency guards, which is the most consequential semantic here.

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?

Names a specific verb ("Undo") and a precise scope ("the top shared manual/MCP history step"), which is narrow enough that an agent can distinguish it from history_redo by the verb alone. The addition of "manual/MCP" clarifies which history stream is affected.

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 rather than stated: the tool applies only to the top step and only within shared manual/MCP history, and "read state afterwards" hints at a follow-up workflow. There is no explicit when-not guidance, such as what happens when the history is empty, and no alternative is named.

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