Skip to main content
Glama

История публикаций опроса

get_quiz_versions
Read-onlyIdempotent

Показывает историю публикаций опроса: каждая публикация оставляет снимок. Черновик в список не попадает — это текущее состояние, а не история. Снимок с is_live — тот, который сейчас видят респонденты. По version_id из этого списка работает restore_quiz_version.

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

Input Schema

NameRequiredDescriptionDefault
limitNoСколько снимков вернуть, от 1 до 100. По умолчанию 20.
offsetNoСколько снимков пропустить от начала списка. Список отсортирован от новых к старым.
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. Beyond that, the description adds genuine domain behavior: snapshots are immutable publication artifacts, drafts are excluded, and the is_live snapshot identifies what respondents currently see — information not available in any structured field.

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?

Four short sentences, each carrying distinct information: what is returned, what is excluded, how to interpret is_live, and which tool consumes version_id. The key scoping constraint (draft exclusion) is front-loaded and there is no redundant restatement of the title.

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?

There is no output schema, so the description carries the burden of explaining the returned records, and it does so adequately by defining snapshot semantics, the is_live flag, and version_id. It could be slightly richer about what other fields a snapshot contains, but nothing needed to call it correctly is missing.

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 description coverage is 100%, and the schema already documents limit, offset, ordering (newest to oldest) and quiz_id, so the description adds nothing about parameters. Baseline 3 applies; the description mentions version_id only as a returned field rather than as an input.

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 names a specific verb+resource pair ('Показывает историю публикаций опроса') and immediately defines the unit returned ('каждая публикация оставляет снимок'). It also separates itself from the sibling restore_quiz_version by clarifying that this list only provides version_id values, so an agent can distinguish the two tools without opening either 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?

It gives explicit inclusion/exclusion rules ('Черновик в список не попадает — это текущее состояние, а не история') and routes restoration work to restore_quiz_version. It stops short of a full when-to-use framing (e.g. when to prefer get_quiz_structure or a report instead), but the scope boundaries are clear.

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