Skip to main content
Glama

Отчёт опроса

get_quiz_report
Read-onlyIdempotent

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

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

Input Schema

NameRequiredDescriptionDefault
date_toNoКонец периода (формат Y-m-d).
quiz_idYesID опроса.
statusesNoСрез по статусам прохождения на этот вызов, любые из: completed (завершили), unfinished (ушли, не дойдя до конца), screenout (дисквалифицированы). Не передан — сохранённый срез отчёта (save_quiz_report_filters), по умолчанию ["completed"]. unfinished и screenout без опции тарифа «незавершённые ответы» отбрасываются; применённый срез — в meta.statuses ответа. Сохранённый срез не меняется.
date_fromNoНачало периода (формат Y-m-d).
is_completeNofalse = отчёт только по незавершённым (как statuses: ["unfinished"]). true или не передан — срез statuses, а без него сохранённый срез отчёта. Устарел, лучше statuses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
      +}
  2. First observed

TDQS

A3.8/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 safety is covered. The description's main added value is the report_uuid output contract for chaining, but it says nothing about report size, latency, or what the persisted slice behavior means for the caller – that nuance lives only in the schema.

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?

Three short sentences, front-loading what is returned, then supported filters, then the output dependency. Nothing is redundant and no sentence could be dropped without losing information.

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?

No output schema exists, and the description discharges the most important return-value fact (report_uuid and its consumers). It does not describe the shape of the 'detailed report' payload itself, which is a minor remaining gap given fully documented input parameters and clear annotations.

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 parameters are documented in detail (statuses enum, tariff filtering, persisted filter semantics, deprecated is_complete). The description only echoes 'срез по статусам' and 'период' without adding format or precedence detail beyond the schema, so 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 and resource ('Возвращает детальный отчёт по виджетам опроса') and names the two siblings that consume its output (get_quiz_report_files, get_quiz_report_inputs). It does not explicitly differentiate itself from other report-like siblings such as get_quiz_summary or get_ai_report, so it falls short of a 5.

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

Usage Guidelines4/5

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

Gives a usable workflow condition: call this to obtain a report_uuid that the files and inputs tools require, and states the supported dimensions (statuses, period). No explicit when-not guidance or prerequisite (e.g. plan/tariff limits) is given in the description itself.

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