Skip to main content
Glama

FoodSafetyData.io

get_safety_profile

Full public-data profile for one establishment: registry identity, Salmonella verification history, lab sampling results, recalls, and a neutral reported-status summary with the USDA source URLs behind it.

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

Input Schema

NameRequiredDescriptionDefault
codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: 'public-data' signals read-only non-sensitive access, and it discloses the content shape (identity, verification history, sampling, recalls, status summary) plus the provenance of USDA source URLs. It does not state behavior for an unknown or invalid code, nor any rate or freshness limits, which keeps it below a 5.

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?

One front-loaded sentence that leads with the scope ('Full public-data profile for one establishment') and then lists exactly what is returned. The enumerated content all earns its place; there is no filler or restatement of the tool name.

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?

Without an output schema, the description is the only source of return-value information, and it does list the constituent sections reasonably well, so an agent knows roughly what to expect. However, for a data-heavy lookup tool it omits the identifier format for 'code', any notion of result size or pagination, and failure behavior, leaving real gaps.

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 description coverage is 0%, so the description must explain the single parameter, but it only says 'one establishment' and never clarifies what 'code' is — an establishment ID, a USDA establishment number, or a numeric key. An agent could easily pass the wrong identifier form, and nothing in the definition mitigates that.

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 states a specific verb and resource — a full public-data profile for one establishment — and enumerates the sections returned (registry identity, Salmonella verification history, lab sampling, recalls, status summary). It is clearly a single-entity read, which implicitly separates it from the search/list sibling, but it never names or contrasts with lookup_establishment, so the differentiation is inferred rather than stated.

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 by 'for one establishment' and 'Full public-data profile', suggesting it is the deep-dive call once a specific establishment is identified. There is no explicit when-to-use or when-not-to-use guidance and no pointer to the sibling tools for searching or lightweight lookup, leaving the agent to infer routing.

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