WebAsk MCP

Отчёт опроса

get_quiz_report

Read-onlyIdempotent

Возвращает детальный отчёт по виджетам опроса. Поддерживает срез по статусам прохождения и период. Возвращает report_uuid, который нужен для get_quiz_report_files и get_quiz_report_inputs.

Input Schema

Name	Required	Description
`date_to`	No	Конец периода (формат Y-m-d).
`quiz_id`	Yes	ID опроса.
`statuses`	No	Срез по статусам прохождения на этот вызов, любые из: completed (завершили), unfinished (ушли, не дойдя до конца), screenout (дисквалифицированы). Не передан — сохранённый срез отчёта (save_quiz_report_filters), по умолчанию ["completed"]. unfinished и screenout без опции тарифа «незавершённые ответы» отбрасываются; применённый срез — в meta.statuses ответа. Сохранённый срез не меняется.
`date_from`	No	Начало периода (формат Y-m-d).
`is_complete`	No	false = отчёт только по незавершённым (как statuses: ["unfinished"]). true или не передан — срез statuses, а без него сохранённый срез отчёта. Устарел, лучше statuses.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026

changedInput schema / properties / is_complete / description

Previous value: -"Только завершённые ответы (по умолчанию true)."New value: +"false = отчёт только по незавершённым (как statuses: [\"unfinished\"]). true или не передан — срез statuses, а без него сохранённый срез отчёта. Устарел, лучше statuses."

addedInput schema / properties / statuses

Added value: +{
+  "description": "Срез по статусам прохождения на этот вызов, любые из: completed (завершили), unfinished (ушли, не дойдя до конца), screenout (дисквалифицированы). Не передан — сохранённый срез отчёта (save_quiz_report_filters), по умолчанию [\"completed\"]. unfinished и screenout без опции тарифа «незавершённые ответы» отбрасываются; применённый срез — в meta.statuses ответа. Сохранённый срез не меняется.",
+  "items": {
+    "enum": [
+      "completed",
+      "unfinished",
+      "screenout"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

First observedSep 30, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds non-obvious behavior: unfinished and screenout statuses are silently dropped without the 'незавершённые ответы' tariff option, the actually-applied slice is echoed in meta.statuses, and the saved filter is left untouched. That is real operational context an agent could not infer from the schema; only return shape of the report body is left unstated.

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 short sentences, zero filler: the first defines the output, the second gives the chaining hook. Everything is front-loaded and nothing repeats the title.

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, yet the description names the key return field (report_uuid) and the applied-filter echo, and explains the tariff-driven status pruning that affects results. Combined with full schema coverage and read-only annotations, an agent has what it needs 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%, and the parameter descriptions already explain statuses defaults, the is_complete deprecation and date formats. The description only restates 'срез по статусам прохождения и период', so it adds no meaning beyond the structured fields — 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?

States a specific verb+resource ('Возвращает детальный отчёт по виджетам опроса') and names the two sibling tools that consume its report_uuid, so the agent can place it in a workflow. It stops short of differentiating itself from nearby readers like get_quiz_summary or get_quiz_answers, and 'отчёт по виджетам' remains somewhat abstract.

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?

Implies usage by listing the supported dimensions (status slice, period) and by saying the returned report_uuid is required for get_quiz_report_files and get_quiz_report_inputs — useful chaining guidance. However, it never states when to choose this over get_quiz_summary or get_quiz_answers, nor any precondition such as needing a saved filter first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All WebAsk MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?