Skip to main content
Glama

Протокол ответа

get_answer_protocol
Read-onlyIdempotent

Протокол ответа: подпись (ответ не менялся после отправки: seal.status intact, edited — правил респондент по ссылке, mismatch — данные не совпадают с подписью, none — ответ без подписи), как респондент подтвердил себя (email, sso, unique_link, password, none) со скрытой почтой, заход (устройство, браузер, страна, город, скрытый IP, робот), время на каждый показанный вопрос, проверки (too_fast, gibberish, duplicate_device), правки респондентом и на тарифе Enterprise — подробный журнал прохождения (уход со вкладки, вставка текста, возвраты к вопросам). Тариф «Премиум» и выше. Только чтение.

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

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.
answer_idYesID ответа этого опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so 'Только чтение' adds nothing new. What does add value is the plan gating: Premium-and-above availability, plus the fact that the detailed passage journal is returned only on Enterprise, meaning some fields will be absent depending on the account tier — important behavioral context not captured by annotations or schema.

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?

It is a single dense but well-organized sentence: the seal status values and check codes are given inline with their meanings, so nothing is padding. The deeply nested parentheticals make it heavier to parse than a short lead sentence followed by a field list would be, but no sentence is wasted.

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?

There is no output schema, and the description carries the full burden of explaining the return payload — which it does field group by field group, including the enumerated seal statuses (intact/edited/mismatch/none), auth methods, quality check codes, and tier-dependent depth. For a two-parameter read tool, an agent has everything needed to call it and interpret the result.

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 both parameters (quiz_id, answer_id) are documented in the schema itself. The description adds no format, constraint, or relationship detail (e.g. that answer_id must belong to quiz_id), so the baseline 3 applies.

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 enumerates exactly what the 'answer protocol' contains (signature/seal status, respondent auth method, visit device/browser/geo, per-question timing, quality checks, respondent edits, Enterprise-only detailed journal), which makes the resource concrete. It lacks an explicit verb and never names a sibling to distinguish itself from tools like get_answer_tags or get_answer_extra_field_values, but the content list is specific enough to route correctly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for auditing a single answer's provenance and integrity, and the 'Тариф «Премиум» и выше' note signals an availability constraint. There is no explicit when-to-use/when-not guidance and no pointer to an alternative for accounts below Premium or for lighter-weight answer data.

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