Skip to main content
Glama

Архив опроса

archive_quiz
Destructive

Архивирует или разархивирует опрос.

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>",
      "archive": "<archive>"
    },
    "name": "archive_quiz"
  }
}

Input Schema

NameRequiredDescriptionDefault
archiveYestrue — в архив, false — из архива.
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether the quiz disappears from active lists, whether answers/reports remain accessible, or whether the operation is reversible in effect.

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?

A single short sentence with no wasted words, front-loading the two modes of operation. It is efficient, though it is terse to the point of omitting useful context.

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

Completeness2/5

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

For a destructive, non-idempotent mutation tool with no output schema, the description leaves key questions unanswered: side effects on the quiz, visibility changes, and what happens on repeated calls. Two fully-required parameters are covered by the schema, but behavior after invocation is not.

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 the schema itself documents that archive=true means into the archive and false means out of it. The description adds no additional meaning, which is acceptable given the schema does the work, but it is a bare baseline.

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 states a specific verb pair and resource ('Архивирует или разархивирует опрос'), which clearly conveys the action. Archiving is not offered by any of the listed siblings, so the purpose is distinguishable in practice, though the description does not explicitly differentiate itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to archive versus unarchive beyond the boolean flag documented in the schema, no prerequisites, and no mention of what state the quiz must be in. The agent must infer all usage conditions from the operation name alone.

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