Skip to main content
Glama

Сводка опроса

get_quiz_summary
Read-onlyIdempotent

Возвращает сводную аналитику опроса: визиты, устройства, география и другие метрики. У опроса на сайте (формат micro) ответ другой формы: признак quiz_type, is_connected и воронка показов на чужой странице — показы, открытия, начатые и завершённые прохождения, отказы и причины, по которым опрос не показали, а ещё summary.result — ответы на первый вопрос с оценкой, шкалой, NPS, «да/нет» или вариантами (средняя и число выбравших каждый вариант) — и summary.by_path[].score, средняя по нему на каждой странице. При is_connected = false опрос ещё не подключён ни к одному сайту, и показов не было. У опроса на сайте date_from и date_to (вместе) ограничивают числа этими днями; by_day всегда за всю жизнь опроса; summary.period — дни, за которые посчитано (null — всё время). Обычный опрос их не учитывает.

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

Input Schema

NameRequiredDescriptionDefault
date_toNoТолько для опроса на сайте: последний день периода, YYYY-MM-DD, включительно. Вместе с date_from.
quiz_idYesID опроса.
date_fromNoТолько для опроса на сайте: первый день периода, YYYY-MM-DD, включительно. Вместе с date_to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / date_from
      Added value: +{
      +  "description": "Только для опроса на сайте: первый день периода, YYYY-MM-DD, включительно. Вместе с date_to.",
      +  "format": "date",
      +  "type": "string"
      +}
    • addedInput schema / properties / date_to
      Added value: +{
      +  "description": "Только для опроса на сайте: последний день периода, YYYY-MM-DD, включительно. Вместе с date_from.",
      +  "format": "date",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare the safe read-only/idempotent profile, and the description goes well beyond that: it discloses that the response shape differs for website quizzes, that is_connected=false means no impressions exist, that by_day always spans the quiz's whole life, and that summary.period is null for all-time. With no output schema, this behavioral disclosure carries real weight.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, but the remainder is a single sprawling sentence stitched together with dashes and nested clauses covering funnel metrics, summary.result, by_path scoring, and period semantics. The information earns its place, but the structure makes it hard to scan.

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 no output schema, the description must explain return values, and it does so in detail for the website-quiz case (funnel, result distributions, per-path scores, period). The ordinary-quiz case is left vague ('и другие метрики'), which is the main remaining gap for a dual-shape tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all three parameters. The description still adds meaning by stating that date_from and date_to work only in combination, apply only to website quizzes, and are ignored by ordinary quizzes – context the per-field schema text does not fully convey.

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?

Starts with a specific verb and resource – 'Возвращает сводную аналитику опроса' – and then splits the result shape by quiz type (ordinary vs. website/'micro'). It never names the overlapping siblings (get_quiz_report, get_quiz_visits, get_ai_report), so the agent gets a clear purpose but no explicit differentiation from alternatives.

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?

Usage is only implied: read it to obtain aggregated analytics. The description does explain a conditional rule (date_from/date_to matter only for website quizzes), but it gives no when-to-use/when-not guidance relative to get_quiz_report or get_quiz_visits, which an agent choosing among many quiz tools needs.

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