Skip to main content
Glama
Sign In
AIops-tools

xcpng-aiops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

undo_list

Read-only

Lists recorded, not-yet-applied undo tokens so you can inspect pending rollbacks and select an undoId to apply.

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

NameRequiredDescriptionDefault
limitNo
targetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses non-obvious behavior: an extra row is read so ``truncated`` is measured rather than inferred, and ``effectVerified=false`` means the reversed change is probable, not confirmed. Neither fact is derivable from annotations or schema, and both affect how an agent interprets results.

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?

Front-loaded with the core purpose, then behavior, then args — a logical order with no filler sentences. It is somewhat long and dense with backtick markup, but every clause carries decision-relevant information, so the length is justified.

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?

No output schema exists, so the description carries the return-value burden and does: it enumerates the entry fields (original tool, inverse tool, human note, undoId, effectVerified) and explains the truncation signal. An agent has everything needed to call and interpret the result.

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 description coverage is 0%, so the description must compensate, and it does: ``limit`` is documented as default 50, capped at 500, and ``target`` is explicitly flagged as unused/accepted only for CLI uniformity. That last point prevents an agent from wasting a call passing a meaningful-looking filter.

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 first line states a specific verb and resource — 'List recorded, not-yet-applied undo tokens' — plus ordering ('most recent first'), which immediately separates it from the write-side sibling undo_apply. An agent can tell what this returns without opening 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 Guidelines5/5

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

It explicitly routes the agent to the alternative ('Use the ``undoId`` with ``undo_apply``') and adds a conditional warning — when ``effectVerified`` is false, check live state before applying and do not report it as a confirmed restore. When-to-use and when-to-be-cautious are both stated.

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

Deploy Server

Other Tools