Skip to main content
Glama

Recall365 — Global Product Recalls

FDA import alert red list

fda_import_alerts
Read-only

Search the FDA Import Alert red lists: firms whose products can be detained at the US border without physical examination. Search by firm name, city or product (e.g. 'laser', 'eye shadow', 'Shenzhen'). Defaults to firms in China.

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_import_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoOutput language: zh = 中文, en = English. Default en.
alertNoImport alert number, e.g. 95-05.
limitNo
queryNoFirm name, city or product keyword. Optional.
sinceNoOnly firms listed on/after YYYY-MM-DD.
countryNoISO code (CN default, HK, IN, VN…) or ALL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds valuable domain semantics about what a red-list entry means operationally (detention without physical examination) but says nothing about result ordering, pagination, or how the limit interacts with a broad query.

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, zero filler. The capability and the domain meaning of the data are front-loaded, followed by the searchable fields and the default scope constraint.

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 six-parameter, read-only search tool with a well-covered schema and no output schema, the description supplies enough to call it correctly. The remaining gap is minor: it does not hint at what a returned record contains or how alert numbers relate to queries, though the schema covers those parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 83%, setting a baseline of 3, and the description earns an extra point by illustrating the open-ended query parameter with concrete example tokens ('laser', 'eye shadow', 'Shenzhen') and by restating the China scope default that governs filtering behavior.

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 ('Search the FDA Import Alert red lists') and immediately defines the domain concept: firms whose products can be detained at the US border without physical examination. That framing plus the example keywords makes it unmistakably distinct from the recall-oriented siblings.

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?

The description gives context for what the data represents and how to search it ('by firm name, city or product'), and notes the China default. However, it never says when to pick this over precheck_product or search_recalls, and offers no exclusions or prerequisites.

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