Skip to main content
Glama

QuiroAds Clinic Marketing Tools

Calculate a clinic's lead funnel

calculate_lead_funnel
Read-onlyIdempotent

Works out a health clinic's lead follow-up metrics from its own weekly counts, per source (all, Meta, Google, website, phone, other): contacted ÷ leads, booked ÷ leads, attended ÷ booked and lead → patient, the median time to first response and, with ad spend, the cost per lead, per booking and per new patient. A metric without its counts comes back as pending with the count it needs; nothing is filled with averages. Counts only: never send names, phone numbers or other lead data.

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": {
      "rows": "<rows>"
    },
    "name": "calculate_lead_funnel"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesOne week of the clinic's own counts, one row per source (each source once; all for every source together): the leads that arrived that week, and how many of them have replied, booked and come so far. Leave out any count the clinic does not have: it is never estimated.
currencyNoCurrency of ad_spend: EUR, GBP, USD or AUD. Without it, money is written as a plain number.

Output Schema

NameRequiredDescriptionDefault
noteYes
rowsYes
footerYes
currencyYes
referenceYesThe lead follow-up skill's published reference (Spain, chiropractic): not a target

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavioral context: metrics lacking counts return as 'pending' with the missing count named, and no averages are ever substituted. The privacy constraint ('never send names, phone numbers or other lead data') is a further useful operational rule not captured in 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?

The metric enumeration is front-loaded and the pending/privacy rules follow in short sentences; no filler. The opening sentence is dense with metric formulas, but each element earns its place as output-shaping 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?

With annotations, a fully described schema, and an output schema, the definition covers what an agent needs: inputs are counts only, missing counts are never estimated, and incomplete metrics surface as pending. Only situational guidance (when this tool rather than a sibling) is absent.

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 100%, so every field (leads, booked, contacted, attended, ad_spend, median_first_response_minutes, source, currency) is already documented in the schema. The description restates the per-source breakdown and the ad_spend consequence, adding little meaning beyond what structured fields provide; 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?

States a specific computation (lead follow-up metrics) on a specific resource (a clinic's weekly counts per source) and enumerates exactly which metrics are derived (contacted÷leads, booked÷leads, attended÷booked, lead→patient, median time to first response, cost per lead/booking/patient). This is far from the sibling tools, which deal with care plans, playbooks, ad copy, and a general about tool.

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?

The description implies usage through its input contract ('counts only', 'leave out counts the clinic does not have') but never says when to pick this over the siblings or when the tool is inappropriate — e.g. no statement about pre-launch clinics or sources with insufficient data beyond the pending note.

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