Skip to main content
Glama

UK Data: UK trade, property and planning

cqc_search

Read-onlyIdempotent

Find CQC-registered care homes, GP practices, dentists, hospitals and home care services in an area of England (by postcode, town or local authority), optionally filtered by name, care homes only, or rating (Outstanding, Good, Requires improvement, Inadequate). (cost: 1 credit)

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

Input Schema

NameRequiredDescriptionDefault
nameNostring, optional words to match
townNostring
limitNonumber 1-200
ratingNoOutstanding|Good|Requires improvement|Inadequate
careHomeNoY|N
postcodeNostring
serviceTypeNostring, e.g. Hospital
localAuthorityNostring, e.g. Barnet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / careHome
      Added value: +{
      +  "description": "Y|N",
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"number"New value: +"number 1-200"
    • addedInput schema / properties / localAuthority
      Added value: +{
      +  "description": "string, e.g. Barnet",
      +  "type": "string"
      +}
    • changedInput schema / properties / name / description
      Previous value: -"string"New value: +"string, optional words to match"
    • addedInput schema / properties / rating
      Added value: +{
      +  "description": "Outstanding|Good|Requires improvement|Inadequate",
      +  "type": "string"
      +}
    • addedInput schema / properties / serviceType
      Added value: +{
      +  "description": "string, e.g. Hospital",
      +  "type": "string"
      +}
    • addedInput schema / properties / town
      Added value: +{
      +  "description": "string",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile needs no restating. The description adds two genuinely useful facts beyond them: the operation costs 1 credit and is scoped to England only. It says nothing about result volume, pagination, or how limit interacts with the search.

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 sentence that puts the resource and geography before the optional filters and trailing cost note. It is dense but every clause carries information; only the parenthetical credit note feels slightly bolted on.

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 output schema, the description should say what comes back, and it does not describe the result shape (provider names, addresses, ratings, IDs). Otherwise it covers what the tool searches, where, which filters exist, and the cost, which is adequate for an eight-parameter read-only search.

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%, so all eight parameters are already documented, and the description largely restates them. Its one real addition is implying that an area argument (postcode, town or local authority) is needed despite zero required parameters, plus clarifying that careHome restricts results to care homes. That is marginal value over the schema's own enums and descriptions.

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?

States a specific verb ('Find') and resource set (CQC-registered care homes, GP practices, dentists, hospitals, home care services) with a clear geographic scope of England. It does not mention the sibling cqc_location, which presumably returns details for a single provider, so an agent must infer the list-vs-detail split.

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 phrase 'in an area of England (by postcode, town or local authority)' hints that an area input is expected, and 'optionally filtered by' signals the filters are optional. There is no explicit when-to-use, when-not-to-use, or named alternative such as cqc_location or nhs_organisations.

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