Skip to main content
Glama

search_device_recalls

Retrieve FDA medical device recall enforcement reports by applying filters like product description, recalling firm, classification, and status.

Instructions

Search FDA device recall enforcement reports

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
product_descriptionNoProduct description or name
recalling_firmNoName of the recalling firm
classificationNoRecall classification (Class I, Class II, Class III)
statusNoRecall status
product_codeNoFDA product code
date_fromNoStart date for recall initiation (YYYYMMDD format)
date_toNoEnd date for recall initiation (YYYYMMDD format)
limitNoMaximum number of results to return (1-100)
skipNoNumber of results to skip for pagination
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the tool searches reports but doesn't mention if it is read-only, pagination behavior, or what happens on errors. Schema hints at filtering but description lacks transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is too minimal for a 9-parameter tool. It lacks structure and does not earn its place by providing useful context beyond the tool name.

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

Completeness2/5

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

Despite 9 parameters and no output schema, the description is only one line. It does not explain return values, result structure, or how to combine filters. The description is insufficient for the tool's complexity.

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 description does not need to add parameter details. The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 clearly states the tool is for searching FDA device recall enforcement reports. It uses a specific verb ('Search') and resource, and the name differentiates it from siblings like search_device_510k or search_device_adverse_events, though no explicit comparison is made.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., search_device_adverse_events). There is no context on prerequisites or typical use cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Augmented-Nature/OpenFDA-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server