Skip to main content
Glama

FoodSafetyData.io

lookup_establishment

Resolve a USDA inspection code from a package label (e.g. P12345, M12345, I135 or a company name) to its establishment: plant name, company, location, status, Salmonella verification categories per product class, and recall history.

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": {
      "code": "<code>"
    },
    "name": "lookup_establishment"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does useful work by spelling out the return payload and by showing accepted input formats (P12345, M12345, I135, or a company name), which signals the acceptable code shapes. It stops short of stating what happens on a miss, whether a company-name lookup can return multiple establishments, or whether the numeric prefix carries meaning.

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?

A single front-loaded sentence with the verb and target in the first three words, followed by the return fields in a compact list. Every clause carries information; nothing is padding or restated from a title.

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 one parameter, no output schema, and no annotations, the description does the heavy lifting well by enumerating the returned fields so the agent knows what it gets back. The remaining gap is edge-case behavior — not-found results and multi-match company-name lookups — which matters more here precisely because nothing else documents it.

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 0% — the single 'code' parameter is documented nowhere in the schema — so the description must compensate, and it largely does. The concrete examples of both accepted forms (inspection codes with varying prefixes, or a company name) are exactly the meaning the schema lacks. It falls short of explaining prefix semantics or name-matching behavior.

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?

States a specific verb (resolve) and resource (establishment) and enumerates exactly what the resolution returns: plant name, company, location, status, Salmonella verification categories, recall history. It does not distinguish itself from the siblings search_establishments or get_safety_profile, so an agent cannot tell from the text alone which of the three to pick when it has no code in hand.

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 rather than stated: the reader infers 'use this when you have a code from a package label.' There is no explicit when-not guidance and no reference to the sibling tools, even though accepting 'a company name' overlaps with what a search tool would plausibly do. One sentence about which tool to use for a name versus a code would raise this substantially.

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