Skip to main content
Glama

Порядок вопросов в карточке ответа

set_answers_order_mode
Destructive

Задаёт порядок вопросов внутри карточки ответа: respondent — в том порядке, в каком человек реально проходил опрос, survey — в порядке вопросов самого опроса. Тот же порядок получают публичная ссылка на ответы и выгрузка в Word, то есть настройка меняет и то, что видят другие.

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

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.
answers_order_modeYesrespondent — как проходил человек, survey — как вопросы идут в опросе.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds genuinely new context that annotations cannot carry: the change propagates to the public answer link and the Word export, i.e. it affects what other people see. It does not say what the previous setting is replaced with or whether permissions/ownership are required, which would have pushed this higher.

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?

Two tight sentences, front-loaded with the core behavior and then the cross-surface consequence. Nothing is redundant and no filler is present.

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 setter with full schema coverage and no output schema, the description covers purpose, enum meaning, and the propagation effect on shared surfaces. The only gap is the absence of any note on required access level or whether the change is reversible, which matters given destructiveHint=true.

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%, with both quiz_id and the enum documented inline, so the schema already does the explanatory work. The description restates the same respondent/survey meanings without adding format, defaults, or side-effect detail per value, 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 names a concrete verb and resource ('Задаёт порядок вопросов внутри карточки ответа') and defines both enum modes in plain language, so an agent can immediately tell what the tool changes. It also distinguishes this setting from the export/share tools by explaining that it governs their output rather than duplicating them.

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?

The two mode values are explained, which implies when each is appropriate, but there is no explicit 'use this when / do not use when' guidance and no named alternative. The note about the public link and Word export hints at downstream consequences but does not say under what circumstances an agent should reach for this tool versus the export tools themselves.

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