Skip to main content
Glama

Contaminants Max Levels

contaminants_max_levels
Read-onlyIdempotent

Codex Alimentarius maximum levels (MLs) for a contaminant in food, lead, cadmium, arsenic, mercury, methylmercury, tin, aflatoxins, ochratoxin A, patulin, melamine, hydrocyanic acid. Returns each commodity with its maximum level, the unit it is expressed in, and the page of CXS 193 it came from. Use for "what is the Codex limit for lead in fish" or "which foods have cadmium maximum levels".

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": {
      "contaminant": "lead"
    },
    "name": "contaminants_max_levels"
  }
}

Input Schema

NameRequiredDescriptionDefault
commodityNoOptional. Narrow to a commodity or food group, e.g. "rice", "fish", "milk", "vegetables".
contaminantYesContaminant name, e.g. "lead", "cadmium", "aflatoxins", "methylmercury", "tin". Matched case-insensitively.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare this as a safe read-only, idempotent, open-world operation, so the description does not need to repeat that. It adds useful behavioral context beyond the annotations by explaining the return shape: each commodity with its maximum level, unit, and source page in CXS 193. It does not cover pagination or how missing contaminants are handled, but the added return context is valuable.

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 purpose is front-loaded and the example queries are practical. The long enumerations of contaminants is somewhat list-heavy, but it is useful scope information rather than filler. Minor trimming is possible, yet the text remains efficient overall.

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 no output schema, the description appropriately explains the return fields and the source (CXS 193). For a simple two-parameter lookup tool this is largely complete, though it omits guidance on how it relates to the similar sibling tool, which would help an agent choose correctly.

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 description coverage is 100%, so the schema already documents both 'contaminant' and 'commodity' fully. The description implies filtering through examples ('lead in fish') but adds no syntax, format, or behavior beyond what the schema provides. Baseline 3 is appropriate.

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 Alimentarius maximum levels) and enumerates the contaminants covered, so an agent can tell what it returns. It does not differentiate from the sibling contaminants_for_commodity, leaving ambiguity about which tool to choose for a commodity-first lookup.

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?

It gives two example questions ('what is the Codex limit for lead in fish', 'which foods have cadmium maximum levels'), which implies when to use it. However, it never names an alternative or states when not to use it, so the guidance is implied rather than explicit.

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.