Skip to main content
Glama

body_undo

Reverses the most recent reversible change, such as a typed value or navigation, and reports when a step is irreversible instead of pretending it was undone.

Instructions

Undo the most recent reversible change (a typed value, a navigation).

Irreversible steps are NOT undone - the journal says so instead of pretending.

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": "body_undo"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations exist, so the description carries the full load, and it does address the key concern: scope is limited to the single most recent reversible change and irreversible steps are explicitly left alone rather than falsely reported as undone. Remaining gaps are what happens when there is nothing to undo and how the outcome is reported.

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?

Two short sentences, front-loaded with the action and followed by the limiting condition. The phrasing 'instead of pretending' is slightly informal but does convey a real behavioral guarantee.

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?

For a zero-parameter mutation with no annotations and no output schema, the description covers scope and the irreversible-change caveat but says nothing about the no-op case or the shape of the result. It is adequate to call the tool safely, but not 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 nothing for the description to disambiguate; baseline 4 applies.

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 and object: undo the most recent reversible change, with concrete examples (a typed value, a navigation). It is clearly distinguishable from siblings like body_undo_list or body_cancel, though those alternatives are never named.

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?

The description implies when to use it (roll back the last reversible action) and draws a boundary around what it will not touch (irreversible steps). It does not point to alternatives such as body_undo_list for inspecting history or body_cancel for aborting in-flight work, so the agent must infer routing.

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