Skip to main content
Glama

Сколько ответов подойдёт

count_quiz_answers
Read-onlyIdempotent

Считает, сколько ответов войдёт в отчёт (section=report) или в список «Ответов» (section=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>",
      "section": "<section>"
    },
    "name": "count_quiz_answers"
  }
}

Input Schema

NameRequiredDescriptionDefault
filtersNoФильтры той же формы, что у generate_filtered_report: даты, period, widgets, tags, country, device, source, viewed, quality, city, exclude и др. Только для section=answers: locale — массив кодов языка опроса и/или "none" (ответы без языка).
quiz_idYesID опроса.
sectionYesreport — выборка отчёта (срез statuses), answers — список «Ответов» (вкладка is_complete / is_screenout / is_deleted, поиск search).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / filters / description
      Previous value: -"Фильтры той же формы, что у generate_filtered_report: даты, period, widgets, tags, country, device, source, viewed, quality, city, exclude и др."New value: +"Фильтры той же формы, что у generate_filtered_report: даты, period, widgets, tags, country, device, source, viewed, quality, city, exclude и др. Только для section=answers: locale — массив кодов языка опроса и/или \"none\" (ответы без языка)."
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower. The description still earns credit for the non-obvious guarantee that counting does not mark answers as viewed, plus the plan-requirement caveat. It does not describe the return shape (a count) or how filters interact across the two sections in any detail, so it adds only moderate value beyond annotations.

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

Conciseness4/5

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

One dense paragraph with the core behavior and the two section modes front-loaded, followed by the non-viewed guarantee and the plan caveat. Every sentence carries information, though the filter/plan notes could be ordered slightly more tightly.

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 3-parameter read-only counting tool with a nested filter object and no output schema, the description covers purpose, section choice, side effects, and entitlement. The only gap is that the return value (a numeric count) is implied rather than stated, which is minor.

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 enum/parameter descriptions already explain section=report vs section=answers and the filter object. The description only restates the section split and mentions filters generically, adding essentially nothing new; the baseline 3 applies.

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?

Names a specific verb (counts) and resource (answers), and explicitly states it does not return the answers themselves, which separates it from get_quiz_answers and the export_* siblings. The two section modes (report vs answers list) are named inline, so an agent can pick the right scope without opening the schema.

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?

It gives clear usage context — use when only a count is needed for a report selection or the Answers list — and adds an entitlement prerequisite ('Нужна опция фильтров результатов в тарифе'). It stops short of naming an explicit alternative or stating when-not to use, so it falls short of a 5.

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