Returns the clinic's published treatment prices in GBP and EUR, per treatment and per full-mouth package.
| Name | Required | Description | Default |
|---|---|---|---|
| treatment | No | Optional treatment id to filter, e.g. all-on-4 |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | ||
| meta | Yes | ||
| evidence | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds context about the output (published, in GBP/EUR, per treatment/full-mouth package) but does not disclose additional behavioral traits like error conditions or data completeness. This is consistent with the moderate effort seen in similar read-only tools.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that clearly states the verb and resource, with no filler or redundant information. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one optional parameter, read-only annotated, output schema present), the description is fully complete. It specifies the exact scope of results and the output schema handles return-value structure, so no additional context is needed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides full coverage of the single optional 'treatment' parameter with an example ('all-on-4'). The description does not add any meaning beyond what the schema already specifies, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific verb ('Returns') and resource ('the clinic's published treatment prices') with additional scope details (GBP/EUR, per treatment and per full-mouth package). This clearly differentiates it from sibling tools like get_treatments or fetch.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when to use this tool: when needing published treatment prices in GBP/EUR. It does not explicitly name alternatives or exclusions, which would warrant a 5, but the scope is specific enough for an agent to infer appropriate usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each get_* tool targets a distinct information domain (clinic profile, doctor profile, prices, reviews, etc.), but the generic 'fetch' overlaps with the specific getters, creating minor ambiguity.
Most tools follow a get_* pattern, but 'fetch' breaks the convention, and 'search' and 'request_callback' deviate from the get_ prefix, resulting in an inconsistent style.
With 12 tools, the set is well-scoped for a patient services server, covering information retrieval and contact actions without bloat.
The server covers the core patient journey: researching treatments, clinic info, prices, reviews, visit logistics, and initiating contact via callback or WhatsApp. A potential gap is direct appointment booking, but the contact mechanisms compensate.
