Skip to main content
Glama

BRAINIAC FDA Drug Device and CQC Location Lookup

Search FDA drug recall enforcement reports

health-codes_fda-drug-enforcement-search
Read-onlyIdempotent

Search vendored openFDA drug enforcement reports by recall number, firm, product text, classification or status. Price $0.03 USDC. POST /api/v1/health-codes/fda-drug-enforcement-search. An unpaid call returns the x402 payment terms and does not run.

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": "health-codes_fda-drug-enforcement-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
firmNofirm, string, length 2 to 200. Optional.
limitNolimit, integer, from 1 to 50. Required.
statusNostatus, string, one of Ongoing, Completed, Terminated. Optional.
productNoproduct, string, length 2 to 200. Optional.
recallNumberNorecallNumber, string. Optional.
reportDateToNoreportDateTo, string, date. Optional.
classificationNoclassification, string, one of Class I, Class II, Class III. Optional.
reportDateFromNoreportDateFrom, string, date. Optional.

Output Schema

NameRequiredDescriptionDefault
totalNototal. Number.
resultsNoresults. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
snapshotDateNosnapshotDate. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: a $0.03 USDC price, the POST endpoint, and the critical fact that an unpaid call returns x402 payment terms without executing. It does not describe result volume or how the payment handshake completes.

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?

Three short sentences, front-loaded with purpose, then cost and transport, then the payment failure mode. Nothing is padded and the most consequential operational fact (unpaid calls do not run) lands last but is not buried.

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?

An output schema exists and annotations are rich, so the description need not explain return values. It covers the payment prerequisite, which is the one thing neither schema nor annotations convey. Minor gap: no indication of result caps beyond the schema's limit maximum of 50 or of pagination behavior.

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% across all eight parameters, including enums for status and classification, a regex for recallNumber and date formats, so the schema does the heavy lifting. The description only restates the filter dimensions already documented in the schema and adds no syntax, default or interaction detail.

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?

States a specific verb ('Search') and a precise resource ('vendored openFDA drug enforcement reports'), then enumerates the filterable dimensions (recall number, firm, product text, classification, status). It is clearly distinguishable in substance from the shortage, 510(k), NDC and Orange Book siblings, though it never names them explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the resource name and the filter list – an agent can infer this is the tool for recall enforcement records rather than shortage or approval data. There is no explicit when-to-use/when-not guidance and no mention of what to do when a query returns nothing or when to prefer a different FDA endpoint.

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.

Resources