Skip to main content
Glama

Fda Compliance Actions

fda_compliance_actions
Read-onlyIdempotent

FDA compliance and enforcement actions taken against a firm, warning letters, injunctions, seizures, debarments, with the action type and the date taken. Search by firm, country, state, product type or date range. Source: FDA Data Dashboard (OII).

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",
      "limit": 25
    },
    "name": "fda_compliance_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
firmNoFirm legal-name substring.
limitNoRows to return (default 50, max 5000).
sinceNoEarliest action date, YYYY-MM-DD.
stateNoUS state, as a postal code ("NJ") or full name ("New Jersey"), both work. Foreign sites carry no state; filter those by country.
untilNoLatest action 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.
countryNoCountry name.
action_typeNoAction type substring, e.g. "Warning Letter".
fiscal_yearNoFDA fiscal year.
product_typeNoe.g. "Drugs", "Devices".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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."
    • changedInput schema / properties / state / description
      Previous value: -"US state, as a postal code (\"NJ\") or full name (\"New Jersey\") — both work. Foreign sites carry no state; filter those by country."New value: +"US state, as a postal code (\"NJ\") or full name (\"New Jersey\"), both work. Foreign sites carry no state; filter those by country."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered without the description. The description adds useful context beyond that: the source system (FDA Data Dashboard / OII) and the fact that each row carries an action type and date. It does not address result volume, pagination, or that the _apiKey is mandatory in practice, which would have raised the score.

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?

Two dense sentences plus a source attribution, with the substantive content (what the data is, what it contains) front-loaded before the search dimensions. No filler, though the source clause is minor overhead for an agent deciding whether to call it.

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 10-parameter, all-optional read query with no output schema, the description covers what the records are, the key returned fields, the filter surface, and provenance. Remaining gaps (row shape beyond action type/date, default limits, credential necessity) are partly handled by the schema and are modest for a lookup tool.

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 100% and the parameter descriptions are unusually detailed, including the _apiKey format and the note that foreign sites carry no state. The prose only restates the filter set at a high level and adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 pair (FDA compliance and enforcement actions against a firm) and enumerates the concrete action types returned: warning letters, injunctions, seizures, debarments. That level of detail clearly separates it from inspection- or citation-oriented siblings, though it never explicitly names an alternative tool.

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?

It lists the available search dimensions (firm, country, state, product type, date range), which implies how to drive the tool, but gives no explicit when-to-use guidance, no statement of when a different sibling (e.g. fda_483_citations or fda_inspections) is the better choice, and no preconditions such as the API credential requirement.

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.