Skip to main content
Glama

body_undo_list

Lists recent body changes and indicates whether each can be undone, helping agents review modifications and avoid irreversible actions.

Instructions

What the body changed and whether it can be undone.

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_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It hints that results include a change summary and an undoability flag, which is useful, but never states that this is a read-only operation, what the ordering or recency semantics are, or whether the history is scoped to a session or the whole body.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

One short sentence with no filler, so nothing needs trimming. However, the brevity comes at the cost of under-specification rather than being efficiently informative.

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

Completeness1/5

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

No annotations, no output schema, and an undocumented parameter mean the description is the only source of truth, and it omits nearly everything needed: the operation, the return shape, and the meaning of limit. For a history-listing tool it is not sufficient to call correctly.

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?

There is a single limit parameter at 0% schema description coverage, and the description says nothing about it. The agent gets no indication of what limit governs, whether it caps entries or days, or its default behaviour beyond the schema's default value of 10.

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

Purpose2/5

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

The sentence reads as a description of a return value ('what the body changed and whether it can be undone') rather than the operation itself. No verb such as list or get is stated, and nothing distinguishes it from the sibling body_undo, which presumably performs the undo.

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 indication of when to call this versus body_undo or any other state-inspection tool, and no prerequisites or exclusions are given. The agent must infer from the name alone that this is a listing of undoable changes at a point in time.

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