Skip to main content
Glama

Codex Commodity Search

codex_commodity_search
Read-onlyIdempotent

Find food commodities in the Codex pesticide residue database by name (apple, rice, milk, poultry meat). Returns each match with the id needed to look up every pesticide limit that applies to it. Codex splits foods finely, "apple" and "apple pomace, dried" are separate commodities with different limits.

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": {
      "query": "apple"
    },
    "name": "codex_commodity_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesFood or commodity name, e.g. "apple".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered and the bar is lower. The description adds useful context — matches carry an id for chained lookups, and splitting means results are narrower than a naive substring match would suggest. It does not state matching behavior (exact vs. partial) or what happens on zero results, which is the main remaining gap.

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?

Three sentences, front-loaded with the action and ending on the highest-value caveat about fine-grained food splitting. No filler, though the parenthetical "(apple, rice, milk, poultry meat)" partially repeats the schema's example.

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

Completeness5/5

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

For a single-parameter, read-only search tool with a fully documented schema and no output schema, this covers what an agent needs: what it finds, what it returns (matches plus an id), and the domain pitfall that would otherwise cause wrong queries. Nothing material is missing.

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 description coverage is 100% with a single well-documented parameter, so the baseline is 3. The description adds real meaning with four spanning examples and the warning that granularity matters, which shapes how specific the query string should be. The example "apple" duplicates the schema's own example, limiting the added value slightly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Find food commodities in the Codex pesticide residue database by name" is a specific verb, resource, and scope, and the closing sentence ("Returns each match with the id needed to look up every pesticide limit that applies to it") positions this as the entry point ahead of the MRL-lookup siblings. The name examples (apple, rice, milk, poultry meat) pin down what counts as a commodity without needing the schema.

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?

It clearly frames the workflow: search by name here, then use the returned id with the pesticide-limit lookups. The note that Codex splits foods finely ("apple" vs. "apple pomace, dried") tells the agent how to interpret and refine queries. There is no explicit when-not-to-use or exclusion of a name-based alternative, so it stops short of a 5.

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.