Skip to main content
Glama

ShowMeOnMap

by com.showmeonmap
OverviewDiscussionsAdmin

Undo the most recent op (gated)

undo

Rewind the workspace cursor by one, re-materializing the state as it was before the last mutation. Does NOT delete any ops — redo will fast-forward. Calling undo at the workspace genesis (cursor === 0, only the CreateWorkspace op is in scope) is a no-op that surfaces an error rather than silently doing nothing. GATED: pass confirmed:true to proceed; otherwise a needs_confirmation envelope is returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
map_idYes
confirmedNoSet to true to confirm this sensitive action. If omitted or false, the call returns a needs_confirmation envelope. Undo rewinds the most recent change; redo restores it.
rationaleNoOptional short label (≤300 chars) for the map edit history, e.g. "add wildfire layer". Omit it to send nothing beyond the tool arguments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / confirmed / description
      Previous value: -"Set to true to confirm this sensitive action. If omitted or false, the call returns a needs_confirmation envelope. Autonomous undo without user intent is a footgun — an agent that decides to \"fix\" something can erase prior work."New value: +"Set to true to confirm this sensitive action. If omitted or false, the call returns a needs_confirmation envelope. Undo rewinds the most recent change; redo restores it."
  2. Changed2 schema fields changed
    • changedInput schema / properties / rationale / description
      Previous value: -"Short audit-log label (≤300 chars) stating the user-facing goal this call serves, e.g. \"add wildfire layer for the user's California query\". Required on every call. Stored in the operations log so map edits stay traceable — we never see your chat history."New value: +"Optional short label (≤300 chars) for the map edit history, e.g. \"add wildfire layer\". Omit it to send nothing beyond the tool arguments."
    • changedInput schema / required
      Previous value: -[
-  "map_id",
-  "rationale"
-]New value: +[
+  "map_id"
+]
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: it discloses that no ops are deleted (aligning with destructiveHint=false), that redo can restore state, and that the gated path returns a needs_confirmation envelope rather than performing the action. The genesis no-op-that-errors behavior is a genuinely useful disclosure no annotation conveys.

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?

Three tight sentences, front-loaded with the core action before the edge case and gating details. Slightly redundant with the schema's own description of the confirmed parameter, but no wasted phrasing.

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 by describing the needs_confirmation envelope. It covers the primary failure mode (genesis) and gating, though it omits the optional rationale label behavior.

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 67% and the schema already describes confirmed and rationale in detail. The description restates the confirmed gating semantics but adds nothing about the undocumented map_id or the rationale label, so it does not materially exceed the schema baseline.

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 resource ('Rewind the workspace cursor by one') with a precise scope constraint ('the most recent op'). It explicitly names the sibling relationship ('redo will fast-forward'), letting an agent distinguish undo from redo without inspecting either schema.

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?

Explains the genesis edge case (cursor === 0 is a no-op that errors) and the gating condition (pass confirmed:true or get a needs_confirmation envelope). It does not fully spell out when to prefer undo over redo, but the contrast sentence gives clear routing context.

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

All ShowMeOnMap toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources