Skip to main content
Glama

Revision Restore

revision_restore
Destructive

Restore a report or datasource revision as the current draft while keeping full version history; publish separately after verification.

Instructions

Restore a revision of this report (or of a datasource attached to it) as the current draft, as Version history > Restore does; history keeps every revision. Reusable datasources need allow_shared_source. Journalled; verified by the new head revision. Publish separately.

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": {
      "revision_number": "<revision_number>"
    },
    "name": "revision_restore"
  }
}

Input Schema

NameRequiredDescriptionDefault
entityNoreport
dry_runNo
entity_idNo
report_idNo
revision_numberYes
allow_shared_sourceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), the description discloses that history keeps every revision, that the operation is journalled and verified by the new head revision, and that reusable datasources require allow_shared_source. 'Publish separately' is a valuable behavioral fact an agent would otherwise miss. It does not mention the dry_run default or rate/permission constraints beyond the shared-source flag.

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?

Four short sentences, front-loaded with the action and outcome, with prerequisites and follow-ups trailing. The telegraphic 'Journalled; verified by the new head revision.' is terse but readable; no filler sentences.

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 return values need not be explained, and the annotations cover the safety profile. However, for a six-parameter mutation tool with 0% schema description coverage, leaving dry_run and the entity_id/report_id distinction unexplained is a real completeness gap.

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% across six parameters, so the description must carry the meaning. It explains allow_shared_source and distinguishes report vs. attached datasource, but says nothing about dry_run (which defaults to true — a critical behavior), revision_number's format, or how entity_id and report_id differ. Half the surface remains opaque.

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?

The description gives a specific verb and resource ('Restore a revision of this report (or of a datasource attached to it)') and states the resulting state ('as the current draft'), which is far more than a restatement of the name. It does not explicitly distinguish itself from the sibling 'operation_restore', so an agent must infer the difference.

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?

It anchors usage with 'as Version history > Restore does' and notes 'Publish separately', implying a follow-up publishing step rather than an alternative tool. There is no explicit when-not guidance and no named alternative for restoring at a different scope, so usage is implied rather than directed.

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