Skip to main content
Glama

undo_list

Lists recorded undo tokens (most recent first) with the inverse tool and verification status, so you can review and apply them via undo_apply. Check effectVerified before applying uncertain reversals.

Instructions

[READ] List recorded, not-yet-applied undo tokens (most recent first).

Each entry names the original tool, the inverse tool that ``undo_apply``
would run, and a human note. Use the ``undoId`` with ``undo_apply``.

``truncated`` is measured — one extra row is fetched — so a capped listing
announces itself instead of looking like the complete set.

Each entry carries ``effectVerified``. False means the original write
lost its response, so the change it reverses is PROBABLE, not confirmed —
check the live state before applying, and do not report the result as a
restore of a state that may never have been reached.

Args:
    limit: Max rows to return (default 50). Re-run with a higher limit when
        the result reports ``truncated: true``.
    target: Unused (undo state is host-local); accepted for CLI uniformity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
targetNo
Behavior5/5

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

With no annotations provided, the description fully discloses behavior: it's a read operation, explains the truncated measurement (one extra row fetched), and details the effectVerified field's implications. No contradictions.

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?

The description is well-structured with clear sections, using markdown for readability. Every sentence serves a purpose, from the initial [READ] tag to the parameter explanations. It is appropriately sized.

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

Completeness5/5

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

Given no output schema, the description comprehensively explains return fields (original tool, inverse tool, human note, effectVerified) and behavioral nuances (truncated, effectVerified handling). It leaves no gaps.

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

Parameters5/5

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

Schema coverage is 0%, but the description thoroughly explains both parameters: limit (max rows, default 50, re-run when truncated) and target (unused, for CLI uniformity). It adds complete meaning beyond the schema.

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?

The description explicitly states it lists recorded, not-yet-applied undo tokens (most recent first), using a clear [READ] tag. It distinguishes itself from siblings like undo_apply and other list tools by specifically detailing its output structure.

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

Usage Guidelines5/5

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

It provides explicit guidance: use the returned undoId with undo_apply, re-run with a higher limit when truncated is true, and check live state before applying when effectVerified is false. It also notes that target is unused.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AIops-tools/Nutanix-AIops'

If you have feedback or need assistance with the MCP directory API, please join our Discord server