Skip to main content
Glama

An FDA import alert

get_import_alert
Read-onlyIdempotent

One FDA import alert by its number (such as 99-19 or 16-81): its subject, how many firms are on its Red List and Green List, the firms listed (optionally only one country's), and FDA's page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "number": "<number>"
    },
    "name": "get_import_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesThe import alert's number, such as '99-19'.
countryNoThe supplier's country: a name such as 'India' or a two-letter code such as 'IN'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so safety is covered. The description adds real value by disclosing the exact return payload (subject, Red/Green List firm counts, firm list, FDA page URL), which the annotations do not provide. It does not mention result-size limits or pagination for alerts with many firms.

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?

One sentence, front-loaded with the core action and number format, then a compact list of returned data. The clause structure is slightly run-on but every clause carries information an agent would otherwise have to guess.

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 correctly compensates by enumerating return fields, and both parameters are addressed. What remains unstated (behavior when the alert number doesn't exist, handling of very large firm lists) is minor for a simple two-parameter read tool.

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 100%, so baseline is 3, and the description goes beyond it: it clarifies that 'country' optionally restricts the firm list to one country's firms, explaining the parameter's effect on output rather than just its type. It also reinforces the alert-number format with examples.

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 ('One ... by its number') and resource ('FDA import alert'), and enumerates the returned fields (subject, Red List/Green List counts, firms, FDA page). It does not explicitly differentiate itself from siblings like get_supplier_record, but the retrieval scope is unambiguous.

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?

Usage is implied: look up a single alert by its number, optionally narrowing the firm list to one country. There is no explicit when-to-use/when-not guidance or named alternative among the sibling tools, leaving the agent to infer selection on its own.

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