Skip to main content
Glama

Undo a change

undo_change

Use when the venue owner wants to undo a change made through update_products, add_products or hide_products. Pass the change_id returned when the change was saved. Undoing an added product removes it (and the category created with it, if left empty), as long as it was not changed after being added; otherwise it is hidden. Two steps: preview without confirm, then confirm: true after the owner agrees. Requires the owner to connect their PRENOTO account.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "change_id": "<change_id>"
    },
    "name": "undo_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNofalse or omitted: preview only. true: undo, only after the owner agreed.
change_idYesReturned by the tool that made the change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the conditional outcome (an added product is removed, along with a category left empty, only if it was not modified afterwards; otherwise it is hidden), the human-in-the-loop gate, and the account-connection requirement. The disclosed removal sits in mild tension with destructiveHint=false, but because it is a scoped reversal of the tool's own prior addition it reads as a revert rather than an independent destructive action; the description does not cover what happens with a stale or invalid change_id.

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 trigger condition, then identifier, then outcome, then workflow, then prerequisite — a logical order with no filler sentences. It is dense for a single paragraph and the nested conditional about the empty category takes a second read.

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

Completeness4/5

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

For a 2-parameter mutation-style tool with no output schema, the description covers trigger, input provenance, edge-case behavior, confirmation workflow, and auth prerequisite. The only omission is what the preview step actually returns, which would help the agent interpret the first call.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it ties change_id to the saving tool and explains the sequencing semantics of confirm (preview first, true only after owner agreement) rather than just restating the boolean.

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?

States a specific verb (undo) and resource (a change), and names the three sibling tools whose changes can be undone (update_products, add_products, hide_products), which lets an agent distinguish it from those siblings without opening their schemas.

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?

Explicit when-to-use trigger (the venue owner wants to undo a change), the exact identifier to supply (the change_id returned when the change was saved), the two-step protocol (preview without confirm, then confirm: true only after the owner agrees), and the precondition that the owner must connect their PRENOTO account.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources