Skip to main content
Glama

Tiquiz Quiz Funnel

Get follow-up email stats

get_email_stats
Read-onlyIdempotent

For one quiz: the follow-up email sequence Tiquiz sends itself (or whether the user chose to send from their own autoresponder), its status (draft, active, paused and why), the sender address really used, what still blocks activation, and per email of the sequence: sent, opened, clicked, unsubscribed, bounced, complaints, open and click rates; plus the account's bounce and complaint health. Opens are approximate (some mail apps open everything); clicks are reliable.

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

Input Schema

NameRequiredDescriptionDefault
quiz_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description still earns credit by disclosing non-obvious behavior: whether emails are sent by Tiquiz or the user's autoresponder, the real sender address used, why a sequence is paused and what blocks activation, and the crucial measurement caveat that opens are approximate while clicks are reliable.

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 content is well front-loaded and every clause carries real information, but it is delivered as a single very long comma-spliced sentence that is hard to parse. Splitting into status/sequence/health sentences would improve scanability without adding length.

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 carries the full burden of explaining return values, and it does so thoroughly — enumerating each metric and the account health fields. The only gap is the absence of an explicit usage rule relative to get_stats.

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?

One parameter (quiz_id) with 0% schema description coverage; the schema only supplies a UUID pattern. The description compensates minimally by framing everything as 'for one quiz', implying the ID selects a single quiz, but adds no detail on format, lookup, or error behavior for a bad ID.

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?

Names a specific resource and scope: the follow-up email sequence for one quiz, plus its status, sender address, activation blockers, per-email metrics and account health. The verb is only implied ('get'), but the returned content is enumerated so precisely that an agent can distinguish it from get_stats or get_quiz.

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 implied by 'For one quiz' — this is the per-quiz email breakdown. There is no explicit statement of when to pick this over get_stats, nor any exclusions or prerequisites (e.g. that the quiz must exist or that email must be configured).

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