Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

fda_recalls_enforcement

Read-onlyIdempotent

FDA Recalls & Enforcement - Drugs, Devices, Food: Real-time structured data extraction feed for FDA Recalls & Enforcement - Drugs, Devices, Food.

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

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum number of records to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety and access profile is fully covered by structured data. The description's only addition is 'real-time,' which conveys data freshness (a genuine behavioral trait), but it says nothing about pagination, result ordering, or what a record contains. With annotations carrying most of the burden, this is a modest contribution.

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

Conciseness2/5

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

The sentence is short but largely redundant: it names the dataset twice and appends 'Real-time structured data extraction feed,' which is filler that does not help an agent decide or invoke. Very little of the text earns its place.

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 zero-required-parameter read-only feed with full annotation coverage and no output schema, the description supplies enough for correct invocation: the data domain and its freshness are stated. What is missing (record fields, whether results are paginated) is low-stakes for a single-optional-parameter list 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?

There is a single optional parameter, maxResults, and the schema description coverage is 100%, so the description adds nothing but is not required to. Baseline 3 applies when the schema already documents the only parameter.

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

Purpose3/5

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

The description identifies the resource domain clearly (FDA recalls and enforcement actions covering drugs, devices, and food), but the operative phrase is the vague 'real-time structured data extraction feed,' which describes a delivery mechanism rather than an action. The sentence effectively restates the name and annotation title instead of stating a verb+resource in its own terms, and it gives no signal about how this differs from the sibling 'global_product_recalls'.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of any alternative. An agent cannot tell from this text whether to pick this tool or global_product_recalls or fda_warning_letters_scraper for a given recall query.

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