Skip to main content
Glama

SolvingHealth federal health data

search_device_recalls

Search FDA device recall records. Use for safety history on an implant or device family before citing it.

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_device_recalls"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoProduct description to match
limitNoMax results, 1-50

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 disclosure burden, and "search" reasonably implies a read-only lookup. However, it says nothing about result ordering, whether the record set is exhaustive, how an empty or omitted query behaves despite zero required parameters, or the 50-result ceiling. For an unannotated tool, that leaves meaningful behavioral gaps.

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 short sentences, both load-bearing: the first establishes what is searched, the second establishes when and why. Nothing is redundant or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (two parameters, no nesting, no output schema), and the description covers what it does and when to reach for it. It does not compensate for the absent output schema by indicating what a recall record contains or how results are ranked, which is the main remaining gap for an agent deciding whether this answer is citable.

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%, with both parameters documented in the schema, so the baseline of 3 applies. The description adds only the framing that a query corresponds to an implant or device family, without clarifying match behavior (substring vs exact) or what a missing q returns.

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 states a specific verb and resource: searching FDA device recall records, and it narrows the domain to devices rather than drugs, which separates it from an adverse-event or label search. It does not explicitly name which sibling to prefer over other FDA lookups, so it stops short of full differentiability from the surrounding search tools.

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?

"Use for safety history on an implant or device family before citing it" gives a concrete triggering scenario, including the intent of verifying before citing. It does not say when not to use it, nor does it point to an alternative when the question is about clearances, adverse events, or trials.

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.