Skip to main content
Glama

undo_list

List recorded, not-yet-applied undo tokens with undo IDs and verification status to review and prepare rollback actions.

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``.

One extra row is read so ``truncated`` is measured rather than guessed from
the row count matching the limit; when it is true, older tokens exist.

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, capped at 500).
    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, the description carries full burden for safety and behavior. It explicitly declares '[READ]' to indicate non-destructive operation, and discloses important nuances: the extra row for accurate 'truncated' detection, the meaning of 'effectVerified' including the warning that false means the change is probable not confirmed, and the instruction to check live state before applying. This is comprehensive and actionable.

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-organized: a concise summary sentence, followed by necessary details about fields, usage, and the warning about effectVerified. Each sentence adds value, and the Args section cleanly documents parameters. Despite length, nothing is verbose or redundant.

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 the tool has no output schema and no annotations, the description fully covers return behavior (entry fields, ordering), pagination semantics (truncated via extra row), parameter behavior, and a subtle data-quality caveat. It leaves no significant questions for an agent and is complete for safe invocation.

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?

The input schema provides only types and defaults with zero description coverage. The description fully compensates: it explains 'limit' (max rows, default 50, capped at 500) and 'target' (unused, accepted for CLI uniformity), adding meaning beyond the schema's bare structure.

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 starts with '[READ] List recorded, not-yet-applied undo tokens (most recent first)', which is a specific verb+resource+scope. It clearly distinguishes this from sibling tools like undo_apply, which applies the tokens, and other list tools for different resources.

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?

The description gives explicit usage context: 'Use the undoId with undo_apply.' It also explains the limit parameter and the purpose of the extra row for measuring truncation. However, it doesn't explicitly contrast with sibling list tools, though the resource type (undo tokens) makes alternatives clear.

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/XCPng-AIops'

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