Skip to main content
Glama

Contaminants For Commodity

contaminants_for_commodity
Read-onlyIdempotent

Every Codex maximum level that applies to one food, "which contaminant limits apply to rice", "what are the Codex limits for milk". Returns each contaminant with its maximum level and unit for that commodity, from CXS 193.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "commodity": "natural mineral waters"
    },
    "name": "contaminants_for_commodity"
  }
}

Input Schema

NameRequiredDescriptionDefault
commodityYesFood or commodity name, e.g. "rice", "fish", "milk", "cereal grains", "natural mineral waters".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, open-world lookup, and the description adds genuine value by naming the underlying standard (CXS 193) and the returned fields (contaminant, maximum level, unit). It omits behavior when the commodity is unknown, whether matching is exact or fuzzy, and whether multiple foods can be matched.

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?

The description is short, front-loaded, and contains no filler, with the two example phrasings conveying intent efficiently. The opening clause is a grammatical fragment, which slightly hurts readability but not economy.

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?

For a one-parameter read-only lookup with full schema coverage, annotations, and no output schema, the description supplies what an agent needs: source standard, return content, and canonical example queries. The remaining gap is not-found/misspelling behavior for composite commodity names like "cereal grains".

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

Parameters3/5

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

Schema coverage is 100% with an example value, so the single commodity parameter is already well documented in structured data. The description reinforces that the parameter scopes to one food but adds no matching semantics or normalized-name guidance beyond the schema. Baseline 3 applies.

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 resource (Codex maximum levels for a single food commodity) with a concrete data source (CXS 193) and a described return payload (each contaminant with maximum level and unit). It stops short of differentiating from the sibling contaminants_max_levels, which reads as a near-identical capability.

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?

The two quoted example queries ("which contaminant limits apply to rice", "what are the Codex limits for milk") imply the usage context well enough to route an agent. However, there is no explicit when-to-use or when-not-to-use statement and no named alternative, so the agent must guess how this differs from contaminants_max_levels.

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.