Get FDA drug recalls and adverse event reports from openFDA. Search 17,000+ recalls and 20M+ adverse events by drug name or company.
| Name | Required | Description | Default |
|---|---|---|---|
| drug | No | Drug name to search (e.g. aspirin, Tylenol) | |
| type | No | recalls (default) or adverse_events | recalls |
| limit | No | Number of results (max 25) | |
| company | No | Company/manufacturer name |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and description does not disclose behavioral traits such as rate limits, data lag, or pagination. Only mentions scale (17k+ recalls, 20M+ events) but not behaviors.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence that efficiently conveys purpose and scale without extraneous words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a simple search tool, but lacks information about return format, error handling, or required permissions. Could be more complete given no output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with clear parameter descriptions. Description adds minimal extra meaning beyond confirming the search by drug or company. Baseline score appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the tool retrieves FDA drug recalls and adverse event reports, with specific verb 'Get' and resource. Distinguished from sibling tools which deal with financial data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool instead of siblings. Implied usage for FDA drug data, but lacks comparisons or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.