Skip to main content
Glama

Fda Firm Risk Profile

fda_firm_risk_profile
Read-onlyIdempotent

One-call FDA regulatory risk profile for a manufacturer: inspection history with the NAI/VAI/OAI split, the CFR sections it is most often cited under, compliance actions taken against it, and import refusals at the border. Resolves the firm name to its FDA establishment identifiers (FEI) so you can see whether several sites are involved. Use this for supplier due-diligence or to check a pharma name before an investment or sourcing decision.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "firm": "Intas"
    },
    "name": "fda_firm_risk_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
firmYesFirm name substring, e.g. "Intas".
limitNoRows to scan per source (default 200, max 5000).
sinceNoOnly count events on/after this date, YYYY-MM-DD.
_apiKeyNoFDA Data Dashboard credential as "email:key", the e-mail the credential was issued to, then the FDA-generated key, joined by a colon.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"FDA Data Dashboard credential as \"email:key\" — the e-mail the credential was issued to, then the FDA-generated key, joined by a colon."New value: +"FDA Data Dashboard credential as \"email:key\", the e-mail the credential was issued to, then the FDA-generated key, joined by a colon."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the description's job is added context, and it delivers: it discloses the name-to-FEI resolution step and that multiple sites may be involved, which materially affects interpretation of the results. The 'rows to scan per source' semantics in the schema imply sampling that could truncate findings, but the description never warns that results may be incomplete at low limits.

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 sentences, front-loaded with the scope-defining enumeration before the usage guidance. The first sentence is dense but every clause maps to a distinct result category; nothing is filler, though the long list format is slightly harder to scan than a bulleted breakdown.

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?

With no output schema, the description carries the burden of explaining return content, and it does so by naming all four result categories plus the FEI resolution output. Minor gaps remain around result shape, whether the FEI mapping is returned as a list, and any pagination or truncation behavior tied to `limit`.

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 all four parameters including the _apiKey credential format are already documented in structured data, establishing the baseline of 3. The description adds only indirect value by framing the firm name as something resolved to FEIs, without clarifying substring-match behavior or how `since` interacts with inspection versus refusal dates.

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?

States a specific verb and resource ('One-call FDA regulatory risk profile for a manufacturer') and then enumerates exactly what the profile contains: inspection history with NAI/VAI/OAI split, CFR citation sections, compliance actions, and import refusals. The 'one-call' framing implicitly distinguishes it from the granular siblings (fda_inspections, fda_483_citations, fda_compliance_actions, fda_import_refusals) that cover a single source each.

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?

Gives explicit positive contexts: supplier due-diligence and pre-investment or pre-sourcing checks on a pharma name. It does not name a when-not condition or point to the single-source siblings for drill-down, so the agent must infer that relationship from the aggregated scope.

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.