Skip to main content
Glama
sec-edgar-fda-b2b-mcp

sec-edgar-fda-b2b-mcp

get_fda_drug_approvals

Read-onlyIdempotent

Fetch recent US FDA New Drug and Biologics License Application approvals to monitor biotech/pharma catalysts and newly cleared therapies. Returns JSON records with drug, sponsor, and approval date.

Instructions

Fetch recent US FDA New Drug Applications (NDA) and Biologics License Applications (BLA).

Use this tool to monitor biotech/pharma FDA approval catalysts and newly cleared therapies.
Returns a JSON array of up to 25 records containing drugName, sponsor, applicationNumber,
activeIngredient, approvalDate, and submissionStatus. Requires the APIFY_TOKEN environment variable.

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": "get_fda_drug_approvals"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_resultsNoMaximum number of recent FDA drug approval records to retrieve (1-100).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • addedInput schema / properties / max_results / description
      Added value: +"Maximum number of recent FDA drug approval records to retrieve (1-100)."
    • addedInput schema / properties / max_results / maximum
      Added value: +100
    • addedInput schema / properties / max_results / minimum
      Added value: +1
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuinely useful context the annotations cannot: the APIFY_TOKEN environment variable requirement and the returned fields. However, 'up to 25 records' conflicts with the schema's max_results ceiling of 100, which is a real inconsistency an agent could trip over.

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, purpose front-loaded, then usage, then return shape and auth requirement. No filler. The only weak spot is the redundant return-field enumeration, which the output schema already carries.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present the description need not enumerate returned fields, and annotations cover safety, so the core is adequately covered. The unresolved conflict between the stated 25-record limit and the 1-100 max_results range leaves an agent unsure how pagination or volume actually behaves for a monitoring use case.

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% and the single max_results parameter is fully documented with range and default, so the schema does the heavy lifting and baseline 3 applies. The description never references max_results and instead asserts a fixed 25-record cap, which adds confusion rather than meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Fetch recent US FDA New Drug Applications (NDA) and Biologics License Applications (BLA)') and scopes it to US FDA approvals, which is clearly distinct from the SEC, Shopify, and YC siblings. An agent can tell immediately what domain this returns.

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

Usage Guidelines4/5

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

'Use this tool to monitor biotech/pharma FDA approval catalysts and newly cleared therapies' gives a concrete use case that maps to a real agent intent. It stops short of stating when NOT to use it or naming an alternative for, say, historical or non-US approvals, so it is context rather than full routing guidance.

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