Skip to main content
Glama

FoxAPIs data sources

FDA approvals

fda_approvals
Read-onlyIdempotent

Search FDA drug approval records by drug or company name: application, sponsor, dates and product details. Costs 5 credits a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "fda_approvals"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoapprovals
queryYesFor example: "aspirin"
max_resultsNoFor example: 3

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 bar is lower, and the description still adds real value: a per-call cost of 5 credits, the fact that an empty answer is not charged, and the requirement for a FoxAPIs key. It stops short of rate limits, quotas, or result-shape details, but it meaningfully exceeds the annotations.

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?

Two sentences, front-loaded with what it searches and returns, followed by cost and auth prerequisites. Every clause carries information; nothing is padding.

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 simple three-parameter read-only search with no output schema, the description covers purpose, returned fields, cost model and credential requirement. The main remaining gap is the undocumented 'type' parameter, which an agent could plausibly need to vary.

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 67%, so some structured documentation exists, and the description clarifies that the query string accepts a drug or company name. However the 'type' parameter (default 'approvals') and 'max_results' are left unexplained by both schema and description, so the coverage gap is not compensated.

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 and resource ('Search FDA drug approval records') and names the returned fields (application, sponsor, dates, product details) plus the searchable dimensions (drug or company name). It implicitly separates itself from literature/clinical-trial siblings by scoping to approval records, though it never names an alternative 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 only implied: search by drug or company name to get approval records. There is no explicit when-to-use guidance versus adjacent tools like pubmed_search or clinicaltrials_search, and no stated exclusions or edge cases. The credit and key notes are operational, not selection guidance.

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