Skip to main content
Glama

Возврат опроса из корзины

restore_quiz

Возвращает удалённый опрос из корзины — со всеми вопросами, логикой и ответами. Опрос снова занимает место в тарифном лимите, поэтому при исчерпанном лимите вернуть не получится. Архив — другое: снять опрос с архива умеет archive_quiz.

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": {
      "workspace_id": "<workspace_id>",
      "quiz_ids": "<quiz_ids>"
    },
    "name": "restore_quiz"
  }
}

Input Schema

NameRequiredDescriptionDefault
quiz_idsYesID опросов, до 100 за раз.
workspace_idYesID workspace. Взять из workspace://list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, the description adds the key operational facts: the restore is a quota-consuming mutation, it fails when the plan limit is exhausted, and nested content (questions, logic, answers) is recovered with the quiz. It does not say what happens when some of the requested quiz IDs are not in the trash (partial success vs error), which matters given idempotentHint=false.

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 sentences, each doing distinct work: what is restored, the quota prerequisite, and the disambiguation from the archive. The core action is front-loaded and there is no filler.

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 two-parameter mutation tool with no output schema, the description covers the action, side effects, failure condition, and alternative. The only real omission is the behavior on mixed or already-restored IDs, which is a meaningful edge case for a batch restore.

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%, so both parameters (workspace_id, quiz_ids, including the 100-per-call cap and the workspace://list hint) are already fully documented in the schema. The description adds no meaning beyond that, so the baseline of 3 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?

The description states a specific verb and resource (restore a deleted quiz from the trash) and defines scope ('со всеми вопросами, логикой и ответами'). It also explicitly distinguishes this tool from the sibling archive_quiz by noting that archive is a different concept.

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?

It gives an explicit precondition that activation depends on (plan limit not exhausted) and explicitly redirects to archive_quiz for the archive case. The boundary between 'trash' and 'archive' is made 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