Skip to main content
Glama
Podcast MCP
by calebn

revert_applied_edit_tool

Restore applied edits to selected records as one History step; use dry_run to preview changes without writing.

Instructions

Restore applied edits as one History step; dry_run plans without writing.

Returns a RestoreResult. Records with restore.state history_only need history_undo.

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": {
      "record_ids": "<record_ids>"
    },
    "name": "revert_applied_edit_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
record_idsYes
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.4
    • addedInput schema / properties / dry_run
      Added value: +{
      +  "default": false,
      +  "title": "Dry Run",
      +  "type": "boolean"
      +}
    • removedInput schema / properties / record_id
      Removed value: -{
      -  "title": "Record Id",
      -  "type": "string"
      -}
    • addedInput schema / properties / record_ids
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "title": "Record Ids",
      +  "type": "array"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "record_id"
      -]New value: +[
      +  "record_ids"
      +]
  2. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / project_path / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / project_path / default
      Added value: +null
    • removedInput schema / properties / project_path / type
      Removed value: -"string"
    • changedInput schema / required
      Previous value: -[
      -  "project_path",
      -  "record_id"
      -]New value: +[
      +  "record_id"
      +]
  3. First observedv0.1.0

TDQS

B3.4/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 does disclose that the operation groups restores into a single History step, that dry_run writes nothing, and that some records can fail to restore and require a different tool. It omits permissions, whether a partial restore is all-or-nothing, and idempotency of repeated reverts, which matter for a mutation tool with zero annotation coverage.

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?

Very short and front-loaded: the core action and the dry_run caveat land in the first clause, with the fallback routing last. The heavy reStructuredText backtick markup and the orphaned "Returns a RestoreResult" fragment add visual noise, but there is no filler prose.

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

Completeness3/5

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

An output schema exists, so the description needn't enumerate RestoreResult fields, and it usefully points at restore.state as a decision signal. Still missing for a multi-record mutation tool are failure/partial-success behavior, the role of project_path, and any indication of scope or permissions.

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. It clarifies dry_run's meaning beyond the boolean type, but says nothing about record_ids (format, whether ids must come from list_applied_edits_tool, behavior on unknown ids) or project_path (when it is required versus null). Two of three parameters gain no semantic meaning.

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 ("Restore applied edits") plus an atomicity claim ("as one History step"), which tells an agent more than the name alone. It also partially distinguishes itself from the sibling history_undo by naming the condition ("Records with restore.state history_only need history_undo"), though the differentiation is conditional rather than systematic.

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?

Gives a concrete routing rule away to history_undo for history_only records, and clarifies that dry_run is the non-writing planning path. It does not state a positive "use this when" trigger (e.g. after applying an edit plan) or any prerequisite such as an approved plan or project scope.

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