Skip to main content
Glama

Codex Vetdrug Mrls

codex_vetdrug_mrls
Read-onlyIdempotent

Get the Codex maximum residue limits for one veterinary drug, broken down by animal species and tissue (cattle muscle, liver, kidney, milk; fish fillet; poultry eggs), with its functional class and the JECFA evaluations behind each limit. Accepts a drug name or numeric id. An empty limit list is meaningful, Codex sets no MRL for substances like chloramphenicol that it judges unsafe at any level.

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": {
      "drug": "abamectin"
    },
    "name": "codex_vetdrug_mrls"
  }
}

Input Schema

NameRequiredDescriptionDefault
drugYesVeterinary drug name ("abamectin") or numeric id ("1").

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 readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description's real addition is interpretive: an empty limit list means Codex judged the substance unsafe at any level, which prevents the agent from retrying or treating it as an error. It still does not distinguish an unknown drug name from a substance with no MRL, which the agent would need to interpret results correctly.

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?

Two tight sentences: the first front-loads what is returned and at what granularity, the second covers input flexibility and the empty-result caveat. Every clause carries information; nothing is redundant or padding.

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 does the work of describing return content (per-species/tissue limits, functional class, JECFA evaluations), which is the key gap it needed to fill. The remaining omission is how ambiguous or unknown drug inputs behave relative to a legitimately empty MRL list.

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 coverage is 100% for the single required 'drug' parameter, including the name-or-numeric-id phrasing, so the baseline is 3. The description reinforces the dual input form and the examples (abamectin, chloramphenicol, one of which returns an empty list) show the parameter's real semantics, which is a modest value-add over the schema.

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?

States a specific verb and resource ('Get the Codex maximum residue limits for one veterinary drug'), then enumerates the breakdown by species and tissue plus the ancillary fields (functional class, JECFA evaluations). The 'one drug' scope plus the MRL domain cleanly separates it from the sibling search tools and from commodity/pesticide MRL tools.

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?

Gives clear context: single-drug lookup, accepts either a name or a numeric id, and warns that an empty limit list is a valid answer rather than a failure. It does not explicitly name an alternative (e.g. the vetdrug search tool) for the case where the caller only has a partial/ambiguous name, so it stops short of full when/when-not 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.