Skip to main content
Glama

BRAINIAC FDA Drug Device and CQC Location Lookup

Look up a CQC-registered care location

health-codes_cqc-location-lookup
Read-onlyIdempotent

Look up a CQC-registered care location in England from the vendored care directory and latest published Overall ratings by location id, name, postcode or provider id. Price $0.03 USDC. POST /api/v1/health-codes/cqc-location-lookup. An unpaid call returns the x402 payment terms and does not run.

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": "health-codes_cqc-location-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoname, string, length 2 to 200. Optional.
limitNolimit, integer, from 1 to 50. Required.
postcodeNopostcode, string, length 2 to 16. Optional.
locationIdNolocationId, string. Optional.
providerIdNoproviderId, string, length 3 to 32. Optional.

Output Schema

NameRequiredDescriptionDefault
resultsNoresults. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
ratingsDateNoratingsDate. String.
directoryDateNodirectoryDate. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, yet the description still adds material context: a $0.03 USDC price, the x402 payment protocol, and the important failure mode that an unpaid call returns payment terms and does not execute. It also names the data provenance (vendored directory plus latest published ratings), which tells the agent how fresh results are.

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?

Three sentences, front-loaded with the purpose and data sources, then payment model, then endpoint. The raw POST path is mildly redundant for an agent but is defensible for an HTTP-bridged paid tool; no sentence is filler.

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?

An output schema exists, so return values need not be explained, and the description covers provenance, lookup keys, and payment gating well. The remaining gap is that with zero required parameters it does not say what an unfiltered or no-match call produces, leaving the agent to infer behavior from the schema alone.

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 description coverage is 100%, so the baseline is 3. The description restates the four lookup keys already documented in the schema but omits the fifth parameter (limit) and adds no semantics such as whether name/postcode matching is partial, how multiple filters combine, or what an unfiltered call returns.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (look up), a specific resource (CQC-registered care location in England), the underlying data sources (vendored care directory plus latest published Overall ratings), and the four lookup keys. An agent can distinguish this immediately from the FDA-oriented siblings without opening any schema.

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 by naming the four accepted lookup keys (location id, name, postcode, provider id), which suggests when this tool applies. However, there is no explicit when-not guidance, no statement about whether filters combine or which key to prefer, and no routing to alternatives for the cases this tool does not cover.

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