Skip to main content
Glama

Tiquiz Quiz Funnel

Diagnose a quiz

diagnose_quiz
Read-onlyIdempotent

Run Tiquiz's own checks on one quiz and return a list of findings, each with a severity (blocking, warning, info), what is wrong, and the fix to propose. Covers: results that can never be obtained or ties (profiles mode), score ranges with gaps or overlaps (scoring mode), questions with fewer answers than results, the step where most people leave (only when the sample is large enough), the consent checkbox without a privacy policy, CRM connection and missing tags, and follow-up emails (activation blockers, bounces, writing issues). Findings are computed, not guessed: present them as they are, and apply no fix without the user's explicit yes.

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

Input Schema

NameRequiredDescriptionDefault
quiz_idYes
check_tagsNoAlso ask the CRM which expected tags are missing (read only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered; the description adds genuinely new behavior: findings are 'computed, not guessed' and must be presented verbatim, some checks are conditional ('only when the sample is large enough'), and no remediation without explicit consent. It does not quantify cost or latency of the CRM lookup behind check_tags.

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?

The action and return shape come first, followed by the check inventory and a guardrail sentence. The long middle enumeration is dense but each item earns its place by telling the agent what classes of problems to expect; it could be tightened slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by specifying the return structure (severity levels blocking/warning/info, the problem, and the proposed fix). Combined with the annotation safety profile and the consent guardrail, an agent has everything needed to call it and interpret results.

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 description coverage is 50%: check_tags is documented in the schema, and quiz_id carries a UUID pattern that conveys its format. The description adds no meaning beyond that — 'one quiz' only loosely maps to quiz_id — which is acceptable given the trivial parameter set but leaves nothing extra.

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 and resource ('Run Tiquiz's own checks on one quiz') and enumerates exactly what the checks cover — profiles/scoring modes, answer-count mismatches, dropout step, consent/CRM issues, follow-up emails. This clearly separates it from the sibling getters (get_quiz, get_stats) which retrieve raw data rather than computed findings.

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?

The coverage list makes the intended situation clear (validate a quiz's configuration, results, consent, CRM and email setup) and the closing sentence prescribes agent workflow after the call ('apply no fix without the user's explicit yes'). It stops short of naming when-not-to-use or pointing at a sibling, so it is clear context rather than explicit routing.

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