Skip to main content
Glama

Tiquiz Quiz Funnel

Get statistics

get_stats
Read-onlyIdempotent

Return statistics computed by Tiquiz, identical to its Results and Stats screens. Do not recompute them. With quiz_id: lifetime funnel (views, starts, completions, leads, capture rate), the period's totals and the previous period's, drop-off per question with the question where people really stop (only when the sample is large enough), the full journey from arrival to email, and how leads split between results. Without quiz_id: the same period totals for the whole account and quiz by quiz. Figures are read live when you call; Tiquiz does not push alerts into the conversation. Losing visitors along a quiz is normal: change one thing at a time, then wait for 20 to 30 new answers before judging.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNo30d
compareNoAlso return the previous period of the same length (not available for 'all').
quiz_idNoOne quiz in detail. Omit for an account overview, quiz by quiz.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive, so the description adds real value on top: figures are read live at call time rather than pushed as alerts, and drop-off per question only appears when the sample is large enough. It does not disclose cost, latency, or the concrete response shape, which keeps it from a 5.

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 statement and organized by the with/without quiz_id split, which is the decision the agent must make. Dense but nearly every clause carries content; the closing advice about changing one thing at a time is helpful but sits at the edge of scope for a tool definition.

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, so the description carries the burden of describing returns, and it does so in detail for both modes: funnel stages, period and previous-period totals, drop-off per question, journey to email, and lead splits. It is appropriately sized for a three-parameter analytics tool; exact field names and structure remain unspecified, which is a minor residual gap.

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 67% and the description compensates meaningfully, spelling out what changes when quiz_id is present versus absent and noting that period totals come with the previous period. It does not explain the 7d/30d/90d/all period values beyond what the enum already conveys, and the 'all' versus compare interaction is left to the schema note.

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?

Specific verb plus resource ('Return statistics computed by Tiquiz') and it clearly splits the two operating modes: quiz-level funnel versus account-wide period totals. It also distinguishes itself from ad-hoc computation with 'Do not recompute them.' It does not name sibling tools such as get_email_stats, so routing across the family is left to inference.

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 explicit mode selection: supply quiz_id for one quiz in detail, omit it for an account overview quiz by quiz. Adds interpretive guidance about allowing 20-30 new answers before judging changes. Missing an explicit pointer to when get_email_stats or diagnose_quiz would be the better choice.

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