Skip to main content
Glama

What changed at FDA this week

get_food_import_changes
Read-onlyIdempotent

Food import news from FDA's records over the last 7 days: firms added to or taken off import alert Red Lists, food warning letters FDA posted, foreign food plants FDA classified Official Action Indicated, and how many food shipments FDA reported refusing, with the commonest charges.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety needs no restating. The description adds meaningful behavioral content beyond that: the exact 7-day window, the four data categories returned, and the aggregate framing ('how many food shipments ... with the commonest charges'). It does not state result size limits, whether an empty result is possible, or refresh cadence, which are the remaining gaps for a digest tool.

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?

A single dense sentence, front-loaded with the resource and time window, followed by a four-item enumeration that maps directly to the returned sections. Every clause carries information, though the list-of-four construction is heavy and slightly hard to parse at a glance.

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 must explain the return shape, and it does so by naming all four section types plus the shipment count and charges summary. For a zero-parameter, read-only digest this is close to sufficient, with only volume/ordering and empty-result behavior left unstated.

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?

The tool takes zero parameters, so the baseline of 4 applies. The fixed 7-day window is stated in the description, but that is scope information rather than parameter meaning, since nothing is configurable.

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 concrete resource (food import news from FDA records) and enumerates four specific content types: Red List additions/removals, food warning letters, OAI-classified foreign plants, and refused-shipment counts with commonest charges. That is far more specific than the title alone. It stops short of explicitly contrasting with siblings like get_import_alert or get_supplier_record, leaving the agent to infer that this is a digest rather than a single-record lookup.

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?

Usage context is clearly scoped: a fixed 7-day lookback and the food domain, which tells the agent this is a recent-changes digest rather than a targeted lookup. There are no explicit exclusions or named alternatives telling the agent when to prefer get_import_alert or check_supplier_list instead, so routing beyond the food/weekly framing is left implicit.

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