A
licenseA
qualityB
maintenanceReal US & Canada dental price data for AI assistants: average costs by procedure, state and city, insurance acceptance, and cheapest-state lookups — backed by open datasets (CC BY 4.0, permanent DOIs).
4
20 npm
MIT
toothache.fyi
Server Details
London dental prices from practices' own sites, next to NHS charges and NHS places. Dated, sourced.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
A3.6/5.0
Scored across 2 tools
Disambiguation4/5
The two tools have largely distinct roles: find_dentist retrieves local practice pricing and NHS patient status, while nhs_charges explains NHS charge bands and exemptions. There is minor thematic overlap because find_dentist also returns NHS charge information, but the boundary is still clear.
Naming Consistency3/5
Both names use snake_case and are readable, but they follow different conventions: find_dentist is action-oriented while nhs_charges is topic-oriented. With only two tools the inconsistency is minor, but it does not form a predictable verb_noun pattern.
Tool Count3/5
Two tools is thin for a dental pricing and NHS charges service, though each has a clear purpose. The surface is focused, but it feels borderline minimal rather than fully well-scoped.
Completeness4/5
The core workflow is covered: finding practices by postcode/treatment and understanding NHS charge bands/exemptions. There are minor gaps such as listing all supported areas or exposing fuller practice details, but agents can mostly work around them.
Available Tools
2 toolsfind_dentistDental prices and NHS places near a postcodeRead-onlyIdempotentInspect
What practices near a London postcode district charge for a treatment, lowest first, read by hand from each practice's own price list, with the NHS charge and which nearby practices say they are taking new NHS patients. Covers Tower Hamlets, Hackney, Southwark, Newham, City of London, Islington and Lewisham so far. Every price carries its source page and the date it was read. Always pass on the urgent-care line.
| Name | Required | Description | Default |
|---|---|---|---|
| postcode | Yes | The first half of a UK postcode (the district), e.g. "E14" or "EC1M". Send only that: a full postcode works but only the first half is used. | |
| max_miles | No | How far from the middle of the district. Default 2, the same as toothache.fyi's treatment pages. 1 is walking distance, 6 a short drive. | |
| max_price | No | Budget in pounds. Optional. | |
| treatment | Yes | What the person needs. "emergency" for pain now; "checkup" if unsure; "implant" means the implant and its crown for one tooth. |
nhs_chargesNHS dental charges in EnglandARead-onlyIdempotentInspect
The NHS dental charge bands in England, what each covers, who is exempt, and how to get urgent care, to compare with a private quote.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
A3.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the agent knows this is a safe, repeatable, closed-domain lookup. The description adds useful scope (England-only, covers exemptions and urgent care), but omits a material trait for a charges reference: whether the figures are current, which fee year they reflect, and that they change annually.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence that names the resource and its contents with no filler. Every clause adds a distinct content domain or the intended use case.
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 parameters and no output schema, the description only needs to convey what content comes back, which it does across four domains. The remaining gap is recency/versioning of the charge figures, which matters for a pricing reference but is a modest omission.
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?
The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter-level information is missing or confusing.
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 clearly identifies a static reference tool and enumerates its content domains (charge bands, what each covers, exemptions, urgent care) scoped to England. It is distinguishable from the sibling find_dentist, which locates providers rather than pricing information, though the distinction is implicit.
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?
"To compare with a private quote" implies one usage context, giving the agent a reason to call it. However, there is no explicit guidance on when not to use it, no mention of the find_dentist sibling, and no statement of prerequisites or limits of applicability.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
find_dentist2 fields changed- changed
Input schema / properties / treatment / descriptionPrevious value: -"What the person needs. \"emergency\" for pain now; \"checkup\" if unsure."New value: +"What the person needs. \"emergency\" for pain now; \"checkup\" if unsure; \"implant\" means the implant and its crown for one tooth." - changed
Input schema / properties / treatment / enumPrevious value: -[ - "checkup", - "emergency", - "hygiene", - "filling", - "extraction", - "rootcanal", - "crown", - "whitening" -]New value: +[ + "checkup", + "emergency", + "hygiene", + "filling", + "extraction", + "rootcanal", + "crown", + "whitening", + "implant" +]
2 tool updates
- First observed
find_dentist - First observed
nhs_charges
Related MCP Connectors
Sourced US and Canadian dental prices, Medicaid and Medicare dental rules, treatment-plan checker.
See your dental clinic's free slots, dentists, treatment prices and how busy each day is.
Factual UK ADHD & autism assessment price and wait comparison. Read-only; not medical advice.
Find UK vets and pet-care providers, and what practices and retailers charge.
Related MCP Servers
- FlicenseNot gradedqualityBmaintenanceQuery current and historical UK official figures (tax bands, minimum wage, benefits, energy price cap and 100+ more) with effective dates and links to official government sources. Data refreshed whenever the official sources change.-
- AlicenseNot gradedqualityBmaintenanceReal prices people actually paid (homes, rents, fuel, energy, groceries, medicines) from official open data, with source, period, sample size and licence on every answer. Read-only, no API key.MIT
- AlicenseNot gradedqualityCmaintenanceToken cost math for LLM API calls: current per-million-token rates for 69 models across 17 providers, with local arithmetic for estimates, comparisons and monthly budgets. Rates are verified and date-stamped.19 npm2MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.