Skip to main content
Glama

FoodSafetyData.io

search_establishments

Search the USDA establishment registry by inspection code, company or plant name, or city — returns matching establishments with codes and profile URLs.

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": {
      "q": "<q>"
    },
    "name": "search_establishments"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 disclose the return payload shape ('codes and profile URLs'), which is genuinely useful, but says nothing about result caps, pagination, matching behavior (exact vs partial), empty-result handling, or authentication.

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 tight sentence, front-loaded with the verb and resource, then the search keys, then the return value. Nothing is padded; the only mild weakness is that the return-value clause crowds the same sentence as the query semantics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with no output schema and no annotations, the description covers purpose, query keys, and roughly what is returned — enough to call it. It falls short on the limit parameter and on how results are ordered or bounded, which an agent would need to use it confidently.

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

Parameters2/5

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

Schema coverage is 0% — neither q nor limit has any description in the schema. The description does explain what q accepts (inspection code, company/plant name, or city), but the limit parameter is never mentioned, so half the inputs remain undocumented anywhere.

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?

Names a specific verb and resource ('Search the USDA establishment registry') and enumerates the accepted search keys (inspection code, company/plant name, city) plus what comes back (codes and profile URLs). It implicitly contrasts with a single-record fetch, though it never names lookup_establishment to make the distinction explicit.

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 only implied: the listed query keys suggest when a search is appropriate (broad lookup by name/city/code), but there is no explicit when-to-use or when-not-to-use guidance, and no mention of the sibling tools lookup_establishment or get_safety_profile as alternatives.

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