Skip to main content
Glama

undo

Revert recent map edits up to 20 steps and restore the previously open map after creating, opening, or building a region.

Instructions

Undo the last change (up to 20 steps). After new_map, open_map or build_region, undo first brings back the map that was open before (with its own undo history).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "undo"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it delivers the two facts an agent could not infer: a 20-step history depth and the fact that history is scoped per map, so undo can swap maps rather than revert a drawing action. It omits the no-op/empty-history case and whether a description of the reverted change is returned, which keeps it short of 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.

Conciseness5/5

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

Two sentences, front-loaded with the primary effect and depth limit, then the exception. Every clause carries information an agent needs; nothing is repeated from the schema.

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?

For a zero-parameter tool with no output schema, the critical unknowns are depth and interaction with map-switching operations, and both are covered. A brief note on empty-history behavior would make it fully complete.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline is 4. The description correctly introduces no parameter discussion and spends its length on behavior instead.

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

Purpose5/5

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

States a specific verb and effect ('Undo the last change') plus a concrete depth bound ('up to 20 steps'). The second sentence names the exact sibling tools (new_map, open_map, build_region) whose prior invocation changes undo's semantics, so an agent can distinguish this tool's behavior from a naive revert.

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

Usage Guidelines4/5

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

Gives a concrete condition under which undo behaves unexpectedly: after new_map, open_map or build_region it first restores the previously open map and that map's own history. It does not state when to prefer undo over any corrective alternative (e.g. remove_objects) or what happens when nothing is left to undo, so it is clear context without explicit exclusions.

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