Skip to main content
Glama

How many answers match

count_quiz_answers
Read-onlyIdempotent

Counts how many answers the report (section=report) or the "Answers" list (section=answers) would show with the given filters, without fetching the answers. Answers are not marked as viewed. Requires the results filters plan option.

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
filtersNoFilters of the same shape as in generate_filtered_report: dates, period, widgets, tags, country, device, source, viewed, quality, city, exclude, etc. Only for section=answers: locale — an array of survey language codes and/or "none" (answers without a language).
quiz_idYesQuiz ID.
sectionYesreport — report selection (statuses slice), answers — the "Answers" list (is_complete / is_screenout / is_deleted tab, search).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / filters / description
      Previous value: -"Filters of the same shape as in generate_filtered_report: dates, period, widgets, tags, country, device, source, viewed, quality, city, exclude, etc."New value: +"Filters of the same shape as in generate_filtered_report: dates, period, widgets, tags, country, device, source, viewed, quality, city, exclude, etc. Only for section=answers: locale — an array of survey language codes and/or \"none\" (answers without a language)."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower, yet the description adds real value: answers are NOT marked as viewed (a side effect an agent would otherwise assume) and the tool requires the results filters plan option. It does not describe cost/pagination, but for a count-only tool that is minor.

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?

Front-loaded with the core action, followed by two short clarifying sentences with no filler. The first sentence is dense with parentheticals but each clause carries distinct 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?

Covers the non-obvious pieces for a nested-filter counting tool: section distinction, filter shape reference to generate_filtered_report, plan prerequisite, and the no-viewed-marking side effect. Nothing about the return value is needed since the count result is self-evident from the description.

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 already documents quiz_id, the section enum semantics, and the nested filters locale nuance, so the schema carries the load. The description only restates the section meanings and points at generate_filtered_report for filter shape, adding little beyond the schema.

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 (counts) plus the resource (answers in a report or 'Answers' list) and explicitly contrasts with fetching the answers, which is what sibling get_quiz_answers does. The section=report / section=answers split makes the scope unambiguous.

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?

"without fetching the answers" implicitly tells the agent to use this instead of a full fetch when only a total is needed, and "Requires the results filters plan option" is a concrete prerequisite. No explicit when-not guidance or named alternative tool, so it stops 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.