Skip to main content
Glama

Выгрузка ответов в Word

export_answers_word
Read-onlyIdempotent

Экспортирует ответы опроса в Word и возвращает ссылку на скачивание (действует 1 час).

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": "export_answers_word"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNoОпциональные ID ответов для включения.
quiz_idYesID опроса.
is_deletedNoБрать удалённые ответы вместо активных (по умолчанию false).
excludedIdsNoОпциональные ID ответов для исключения.
is_completeNoТолько завершённые ответы (по умолчанию true).
is_screenoutNoВключать ответы, дисквалифицированные логикой (по умолчанию false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / excludedIds / maxItems
      Added value: +10000
    • addedInput schema / properties / ids / maxItems
      Added value: +10000
  2. First observed

TDQS

A3.6/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. The description adds genuinely new behavioral context not present in structured fields: the result is a download link that expires after one hour, which matters because the caller must consume it promptly and may need to re-export later.

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?

A single sentence with no filler that front-loads the action and closes with the most operationally important detail, the one-hour link lifetime. Nothing is wasted or buried.

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?

With six fully documented parameters, no output schema, and annotations covering the safety profile, the description covers what an agent needs before calling. The one gap is that there is no mention of scale limits or how the filtering parameters combine when the export set is large.

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 all six parameters — ids, excludedIds, is_deleted, is_complete, is_screenout — carry their own descriptions with defaults. The description adds no further meaning about how these filters interact (e.g., whether ids and excludedIds can be combined), 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 names a specific verb and resource combination — 'Экспортирует ответы опроса в Word' — and adds the return artifact ('ссылка на скачивание'). The output format (Word) implicitly distinguishes it from the CSV/XLSX/SPSS/PDF siblings, though no sibling is actually named for contrast.

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 explicit guidance on when to choose this tool over export_answers_csv, export_answers_xlsx, export_filtered_report_word, or export_quiz_print. The Word format is the only implied selector, and no prerequisites, exclusions, or edge conditions are stated.

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