Skip to main content
Glama

QuiroAds Clinic Marketing Tools

Calculate a clinic's care plan numbers

calculate_care_plan_numbers
Read-onlyIdempotent

Works out a health clinic's care plan numbers from its own monthly counts: first visit → report, report → plan, first visit → plan, plan completed, renewal and reactivation. Given the clinic's own plan options and pay-per-visit price, it adds the price per visit of each option and its saving against paying per visit, largest option first. It never suggests visit counts, frequency, plan length or prices. Counts and prices only: never send patient names or records.

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

Input Schema

NameRequiredDescriptionDefault
visit_1NoPatients whose visit 1 (the assessment) was in the month counted: a count, not a percentage.
visit_2NoOf those, patients who came to visit 2 (the report of findings): a count, not a percentage.
currencyNoCurrency of the prices: EUR, GBP, USD or AUD. Without it, money is written as a plain number.
continuedNoOf those reassessed, patients who continued after the reassessment (new phase or maintenance): a count, not a percentage.
reassessedNoOf those who started a plan, patients who reached the reassessment: a count, not a percentage.
reactivatedNoOf those lapsed patients messaged, patients who booked again: a count, not a percentage.
plan_optionsNoThe clinic's own plan options (one to five), as it already offers them: the visits each includes and its total price. Leave it out if the clinic has none: options are never suggested.
started_planNoOf those, patients who started a plan, as the clinic defines it: a count, not a percentage.
lapsed_messagedNoLapsed patients the clinic messaged to come back: a count, not a percentage.
pay_per_visit_priceNoWhat the clinic charges for one visit paid on its own, in the currency given: with plan_options, it gives each option's saving against paying per visit.

Output Schema

NameRequiredDescriptionDefault
noteYes
plansYesThe clinic's own plan options; null when none are given (the tool never suggests one)
ratesYes
footerYes
currencyYes
referenceYesThe patient retention skill's published reference (Spain, chiropractic): not a target

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses the computation performed on prices, the sort order of results ('largest option first'), and an explicit non-suggestion policy for visit counts, frequency, plan length and prices.

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 core purpose is front-loaded in the first clause, followed by the derived calculations and then the constraints. It is dense but not padded; the closing two sentences about not suggesting prices/plan lengths and not accepting patient records are adjacent constraints that slightly overlap but each carry a distinct rule.

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?

Ten parameters, zero required, an output schema present, and rich schema descriptions mean the return values need not be explained, and the description correctly focuses on inputs and privacy limits. The one gap is that with no required parameters, the description does not indicate whether partial counts produce partial results or an error — useful guidance an agent would need before calling with sparse data.

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?

With schema coverage at 100%, the schema already documents every parameter, so the baseline is 3. The description earns above baseline by explaining the relationship between parameters — that plan_options combined with pay_per_visit_price yields each option's per-visit price and its saving against paying per visit — which is semantic linkage the schema does not state.

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?

The description names a specific verb and resource ('works out a health clinic's care plan numbers') and enumerates the exact conversion steps it computes (first visit → report, report → plan, plan completed, renewal, reactivation), so the agent knows precisely what output to expect. It does not explicitly contrast itself with the sibling calculate_lead_funnel, leaving differentiation to inference from the 'care plan' framing.

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 rather than stated: the description makes clear it consumes a clinic's own monthly counts and prices, and explicitly rules out sending patient names or records. However, it never says when to choose this over calculate_lead_funnel or get_clinic_marketing_playbook, nor what happens if only some counts are supplied.

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