Findabis

Get one clinic in full

get_clinic

Read-onlyIdempotent

One clinic in full: address, hours, fees and price list, CQC record, patient types taken, partner pharmacies, FAQs. Example: {"slug":"green-leaf-clinic"}

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": {
      "slug": "<slug>"
    },
    "name": "get_clinic"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Page slug.

Output Schema

Name	Required	Description
`url`	Yes
`faqs`	Yes	The page's own FAQs, at most five; an answer is marked AI-assisted when the page labels it so
`kind`	Yes
`name`	Yes
`slug`	Yes
`brand`	No
`clinic`	No
`strain`	No
`pharmacy`	No
`description`	Yes
`descriptionAiAssisted`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedInput schema / properties / slug / description

Previous value: -"The page slug from a find_* tool or search_directory, e.g. \"green-leaf-clinic\"."New value: +"Page slug."

AddedNov 8, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, closed-world and non-destructive, so the safety profile is covered. The description adds real value by disclosing the breadth of data returned (fees, CQC record, partner pharmacies), which lets an agent judge whether a full fetch is worth it; it omits only not-found behavior.

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?

A single front-loaded content list plus one example, with no filler or hedging. The colon-separated inventory is dense but readable, and nothing in it is redundant with the schema.

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?

For a one-parameter, output-schema-backed read tool, the definition covers scope and payload well enough to call correctly. The only meaningful gap is the absence of guidance on linking from a find_clinics result or handling an unknown slug.

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 coverage is 100% and the single slug parameter is already documented with a pattern and length bounds. The example value {"slug":"green-leaf-clinic"} usefully confirms the lowercase-hyphenated format the pattern encodes, but adds little beyond the schema; baseline 3 applies.

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 enumerates exactly what a full clinic record contains (address, hours, fees, CQC record, patient types, partner pharmacies, FAQs), which makes the resource and scope unambiguous. It implies a single-record lookup versus the list-returning find_clinics, but never names that sibling, so differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance: nothing says to call this after find_clinics returns a slug, or when to prefer this over get_pharmacy or search_directory. The embedded example implies a slug is required but conveys nothing about the conditions that select this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Findabis tools Inspect

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.