Skip to main content
Glama

search_drugs_at_fda

Search Drugs@FDA for approved drug applications by brand, sponsor, application number, or marketing status; returns application details, products, and submission history.

Instructions

Search the Drugs@FDA database for approved drug applications. Find approved drugs by sponsor, application number, brand name, or marketing status. Returns application details, products, and submission history.

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

Input Schema

NameRequiredDescriptionDefault
skipNoNumber of results to skip for pagination
limitNoMaximum results to return (1-100, default 10)
brandNameNoDrug brand name
sponsorNameNoDrug sponsor/company name
marketingStatusNoMarketing status (e.g., 'Prescription', 'OTC')
applicationNumberNoFDA application number (e.g., 'NDA012345')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv1.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose that this is a read/search operation and sketches the return shape ('application details, products, and submission history'), which is valuable given there is no output schema. It says nothing about rate limits, authentication needs, or the result-cap behavior (limit max 100, default 10, skip-based pagination) that would matter to an agent planning a query.

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

Conciseness4/5

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

Three short sentences, front-loaded with purpose followed by capabilities and return values. Slight redundancy between 'approved drug applications' and 'Find approved drugs', but nothing extraneous.

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?

For a six-parameter, zero-annotation, no-output-schema search tool, the description covers purpose, filterable dimensions, and the rough return contents, which is close to sufficient. The gap is behavioral planning detail: pagination semantics and total-result behavior are not described, so an agent can call it correctly but cannot plan a full result walk from the description alone.

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 every parameter is already documented, and the description only restates the same filter dimensions (sponsor, application number, brand name, marketing status). It adds no syntax guidance such as the expected application number format or whether multiple filters combine with AND. Baseline 3 is appropriate when the schema does the heavy lifting.

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 names a specific verb and resource, 'Search the Drugs@FDA database for approved drug applications', and pins the scope to approved applications rather than the broader drug universe. It also enumerates the filterable dimensions and what is returned, so the tool is distinguishable from label, recall, shortage, or Orange Book siblings. It stops short of naming an explicit sibling, so it lands at 4 rather than 5.

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 phrase 'approved drug applications', which suggests this tool is for regulatory approval records rather than adverse events or patents. However, there is no explicit when-to-use, no when-not-to-use, and no pointer to alternatives such as the Orange Book or drug labels even though those siblings cover overlapping drug questions. The agent must infer the routing decision.

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