Skip to main content
Glama

Возврат к прежней версии опроса

restore_quiz_version
Destructive

Возвращает содержимое прежнего снимка опроса в черновик — это откат неудачной правки. Респондентов откат сразу не касается: живая версия остаётся прежней, пока опрос не опубликуют заново через publish_quiz. Так автор сначала смотрит, что вернулось, и только потом выпускает это наружу. Список снимков — в get_quiz_versions.

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": {
      "quiz_id": "<quiz_id>",
      "version_id": "<version_id>"
    },
    "name": "restore_quiz_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.
version_idYesID снимка из get_quiz_versions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true annotation by scoping the damage precisely: only the draft is overwritten, the live version and respondents are untouched until republish. That is the single most important behavioral fact for a destructive tool and it is stated plainly, along with the intended review-then-publish sequence.

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?

Front-loaded with the action and its consequence, then the audience-impact clarification, then the pointer to the sibling tools. Four short sentences with little waste, though the author-workflow sentence restates the isolation point already implied.

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 destructive two-parameter mutation with no output schema, the description covers what changes, what does not, and what to do next. It stops short of saying whether a restore is itself undoable or what happens on an invalid/expired version_id, which would complete the picture.

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

Parameters3/5

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

Schema coverage is 100% and both parameters are documented there, including that version_id comes from get_quiz_versions. The description repeats that pointer but adds no format, validation, or edge-case meaning beyond the schema, so the baseline applies.

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 concrete verb and resource: it copies a previous snapshot's content into the draft, i.e. a rollback of a bad edit. It explicitly separates itself from publish_quiz (releasing changes) and get_quiz_versions (listing snapshots), so an agent can place it in the workflow 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?

The use case is stated ('откат неудачной правки') and the two surrounding tools are named with their roles: get_quiz_versions to find a snapshot, publish_quiz to make the restored draft live. No explicit when-not-to-use case is given, but the workflow context is unambiguous.

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