Skip to main content
Glama

SolvingHealth federal health data

search_clearances

Search FDA 510(k) device clearances (openFDA). Use to check whether a device type has been cleared, who cleared it, and when — e.g. "is there a cleared knee goniometer", "what did Stryker clear since 2024".

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

Input Schema

NameRequiredDescriptionDefault
qNoDevice name to match, e.g. "knee"
limitNoMax results, 1-50
sinceNoEarliest decision date, YYYYMMDD
applicantNoCompany name, e.g. "Stryker"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the upstream source (openFDA), which usefully signals read-only, public regulatory data, but says nothing about rate limits, API key needs, result ordering, or how the limit cap affects coverage — gaps that matter for an unannotated tool.

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?

Two sentences with the resource and source front-loaded, followed by use cases and examples; no filler. Every clause either identifies the dataset or shows a query pattern the agent can reuse.

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 four-parameter search with full schema coverage, the definition covers purpose, source, and typical queries adequately. The remaining gap is that there is no output schema, and the description does not indicate the shape of returned clearance records or whether results are paginated beyond the 50-item limit.

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?

Schema coverage is 100%, so a baseline of 3 applies, but the examples add real meaning by showing how parameters combine: the knee goniometer example maps to q, and 'what did Stryker clear since 2024' demonstrates applicant + since used together. That is modest but genuine value beyond the schema's per-field descriptions.

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?

Names a specific verb and resource: 'Search FDA 510(k) device clearances (openFDA)', with the data source in parentheses. The example questions ('is there a cleared knee goniometer', 'what did Stryker clear since 2024') make the scope concrete and distinguish it from sibling lookups like search_device_recalls or search_adverse_events.

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

Usage Guidelines4/5

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

Explicitly states when to reach for it: 'Use to check whether a device type has been cleared, who cleared it, and when', with two illustrative scenarios. It stops short of naming an alternative or an exclusion (e.g. 'for recalls, use search_device_recalls'), leaving that to inference.

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.