Skip to main content
Glama

Печатная версия опроса

export_quiz_print
Read-onlyIdempotent

Собирает печатную версию опроса — раздать на встрече, отдать на согласование, заполнить от руки. Форматы: pdf, word, txt, html. Возвращает ссылку на скачивание, действительную час. Речь о самих вопросах, а не об ответах: ответы выгружают export_answers_* .

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_quiz_print"
  }
}

Input Schema

NameRequiredDescriptionDefault
fontNoРазмер шрифта печатной страницы: little, medium (по умолчанию), large.
sheetNoЧто будет на листе — как в разделе «Печать» кабинета. Не передан — лист печатается как раньше. Неуказанное поле берёт значение по умолчанию.
formatNoФормат файла: pdf (по умолчанию), word, txt, html.
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotent, non-destructive), so the description's real contribution is the output behavior: it returns a download link valid for one hour, and it lists supported formats. It stops short of saying whether generation is synchronous or what happens on expiry/regeneration, so it is strong but not exhaustive.

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, front-loaded with the purpose before the format list and the sibling disambiguation. The format enumeration mildly duplicates the schema enum but earns its place as quick scanning context; nothing else 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 supplies the missing return contract (download link, one-hour validity). Combined with the rich nested schema for sheet options and annotations for the safety profile, an agent has everything needed to call this correctly.

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%, including a fully documented nested 'sheet' object with defaults and format-specific caveats (qr/logo not printed in txt, paper/page_numbers only for pdf and word). The description adds no meaning beyond that, which is fine — baseline 3 applies when the schema does the work.

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?

States a specific verb and resource ('Собирает печатную версию опроса') and immediately distinguishes itself from the answer-export siblings ('Речь о самих вопросах, а не об ответах: ответы выгружают export_answers_*'). An agent can route between print export and answer export without opening any schema.

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

Usage Guidelines5/5

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

Gives concrete usage scenarios (hand out at a meeting, send for approval, fill in by hand) and an explicit alternative with the condition that selects it (use export_answers_* for answers). Scenarios plus a named alternative is exactly the when-to-use guidance the dimension asks for.

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