Skip to main content
Glama

restore_report_version

Destructive

Roll a report back to an earlier version (title, default range, panels including queries). Saved as a new version so history is kept. Use when undoing a bad dashboard edit.

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": {
      "reportId": "<reportId>",
      "version": "<version>"
    },
    "name": "restore_report_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYesVersion to restore, from list_report_versions
reportIdYesReport id
expectedVersionNoThe report `version` your edit is based on, from get_report or the last save. The save is rejected if the report changed since. Omit to apply your change to the latest version.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior3/5

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

Adds real context beyond the annotations by disclosing that the restore is persisted as a new version and history is retained, which meaningfully tempers the destructiveHint=true flag. However it does not state that current panel queries/config are overwritten, who may perform it, or what the call returns (e.g. the new version number).

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?

Three short sentences, front-loaded with the action and its effect, then the retention guarantee, then the usage cue. No filler or redundant restatement of the name.

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 three-parameter mutation with a fully documented schema and no output schema, the description covers what changes, the history-preserving behavior, and when to reach for it. The only meaningful gap is the absence of any statement about the result or permission requirements for a destructive operation.

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 value by clarifying that 'version' means the snapshot to roll back to and by framing the operation as replacing title/range/panels. It still does not explain the interaction between version and expectedVersion (concurrency guard) in the description itself.

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?

Names a specific verb ('Roll ... back') and resource ('report', 'earlier version'), and enumerates the scope of what is restored (title, default range, panels including queries). An agent can distinguish it from update_report or get_report without opening the schema.

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 an explicit trigger condition ('Use when undoing a bad dashboard edit') and the schema points at list_report_versions for obtaining the version argument. It stops short of naming the alternative — e.g. update_report for forward edits — or stating prerequisites such as edit permission on the report.

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