Skip to main content
Glama

search_drug_recalls

Search FDA drug recall enforcement reports by product, firm, classification, status, or date to identify withdrawn medications and public health risks.

Instructions

Search drug 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
stateNoState where recall occurred
countryNoCountry where recall occurred
reason_for_recallNoReason for the recall
date_fromNoStart date for recall initiation (YYYYMMDD format)
date_toNoEnd date for recall initiation (YYYYMMDD format)
countNoField to group results by for counting
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, and the description only says 'Search,' which implies a read operation. It does not disclose any behavioral traits such as pagination, data freshness, rate limits, or whether the results are sorted or filtered.

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

Conciseness3/5

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

The description is a single concise sentence, but given the tool has 12 parameters and no output schema, it could benefit from more context. It is adequately sized but not optimally informative.

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?

With 12 parameters, no output schema, and no annotations, the description lacks completeness. It doesn't explain the response format, how parameters combine (e.g., AND vs OR logic), or any limitations.

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 parameters have descriptions in the input schema. The description adds no additional meaning beyond what is already in the schema, meeting the baseline expectation.

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 verb 'Search' and the resource 'drug recall enforcement reports'. It differentiates from sibling tools like search_device_recalls by specifying drug recalls, though it doesn't explicitly mention alternatives.

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 on when to use this tool versus its siblings. The description does not mention when to use it (e.g., to find recall enforcement data) or when not to use it (e.g., for device recalls).

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