Skip to main content
Glama

revert

Undo a prior edit by ID from history; the reversal is logged as a new change.

Instructions

Undo an edit from history(); the reversal is itself logged.

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": {
      "edit_id": "<edit_id>"
    },
    "name": "revert"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
authorNoagent
edit_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important trait: the reversal is itself logged, so the operation appends rather than erases. It omits permissions, what happens if the edit was already reverted, and whether the supplied note/author are attached to the reversal entry.

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?

A single front-loaded sentence with no filler; the source of the identifier and the logging side effect both land in one clause each.

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

Completeness2/5

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

An output schema means return values need not be explained, but this is a three-parameter mutation with zero annotation coverage and undocumented parameters. Nothing covers failure modes (unknown or already-reverted edit_id) or the audit semantics of note/author, which is a substantial gap for an undo tool.

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?

Schema description coverage is 0%, so the description must compensate, and it only implies that edit_id originates from history(). The note and author parameters (and their defaults, including author defaulting to "agent") are never explained, nor is the expected edit_id format.

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

Purpose4/5

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

States a specific verb and resource ("Undo an edit from history()") and ties the operation to the sibling that produces the target, so an agent can tell it apart from history/add_note. It stops short of defining what an "edit" is or what state the target ends in.

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

Usage Guidelines3/5

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

The mention of history() implies the prerequisite workflow (find an edit_id there, then revert it), which is useful implicit guidance. There is no explicit when-to-use/when-not, no statement about reverting a revert, and no named alternative for correcting an edit differently.

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