Skip to main content
Glama

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

export_answers_xlsx
Read-onlyIdempotent

Экспортирует ответы опроса в Excel (XLSX) и возвращает ссылку на скачивание файла (действует 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_xlsx"
  }
}

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds one genuinely useful behavioral trait beyond them: the result is an expiring download link valid for 1 hour, which matters because it is not in any output schema. It says nothing about how long an export of up to 10k answers takes or whether repeated calls produce a fresh link.

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?

One sentence, front-loaded with the action and format, with the link-expiry caveat appended where it is most useful. No filler.

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 six-parameter read-only exporter with full schema coverage and no output schema, the definition covers what is produced and its lifetime. Minor gaps: nothing on how the answer-ID filters combine with the default is_complete=true, and nothing on failure behavior for very large exports.

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%, so all six parameters including the is_complete/is_deleted/is_screenout defaults are already documented in the schema. The description adds no filtering semantics of its own, so the baseline of 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?

States a specific verb (exports), resource (survey answers) and output format (XLSX), which is exactly what separates it from the CSV/SPSS/Word export siblings. It stops short of naming an alternative explicitly, but the format alone is enough to identify it.

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 when-to-use or when-not-to-use guidance; the agent must infer from the format token that this is the Excel path rather than the CSV or SPSS path. No prerequisites, no mention of how the filters interact, no exclusion conditions.

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