Skip to main content
Glama

restore_version

DestructiveIdempotent

Permanently replace a survey's current blocks, questions, and Flow with one of its saved versions, with confirm: true. The current state is not kept, so save or copy it first if it may be needed. To keep the current survey, use create_survey_from_version instead.

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": {
      "survey_id": "<survey_id>",
      "version_id": "<version_id>",
      "confirm": "<confirm>"
    },
    "name": "restore_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true. The survey's current blocks, questions, and Flow are replaced by the snapshot, and the current state is not kept.
survey_idYesThe survey to restore. Must be the survey the version was saved from.
version_idYesVersion to restore (id from read_versions)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds the crucial specifics: what exactly is replaced (blocks, questions, Flow), that the prior state is not retained, and that confirm must be true. That is the 'what gets destroyed' context the annotations alone cannot convey.

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 destructive action, then the data-loss warning, then the safer alternative. No filler or repetition.

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

Completeness5/5

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

For a destructive, confirmed mutation with an output schema available, the description covers the action, the loss of current state, the confirm requirement, and the non-destructive alternative. Nothing an agent needs before invoking it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema itself explains all three parameters, including the confirm gate and the constraint that survey_id must match the survey the version was saved from. The description reinforces the confirm requirement rather than adding new semantics, which is appropriate.

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 ('Permanently replace') and precisely names the resources affected — a survey's current blocks, questions, and Flow — plus the source of the replacement (a saved version). This clearly separates it from create_survey_from_version and the edit_* siblings.

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?

Gives explicit when-to-use (restore a saved snapshot over current state) and when-not-to-use, naming the alternative 'create_survey_from_version' for keeping the current survey. It also states the prerequisite of saving or copying the current state first.

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