Skip to main content
Glama

Codex Vetdrug Search

codex_vetdrug_search
Read-onlyIdempotent

List or search the veterinary drugs for which Codex has adopted maximum residue limits in animal-derived food, antibiotics, antiparasitics, growth promoters. Omit the query to list all of them with the year each was last adopted.

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": "ivermectin"
    },
    "name": "codex_vetdrug_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoDrug name or fragment. Omit to list all.

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?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds context beyond them by disclosing that an unfiltered call returns the full set together with the year each limit was last adopted — a return-content detail that matters here since no output schema exists.

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?

Two sentences, front-loaded with the scope-defining clause and followed by the fallback behavior. The trailing class list ('antibiotics, antiparasitics, growth promoters') is slightly loose but adds real scope information, so little is wasted.

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?

This is a simple, single-optional-parameter read tool with no output schema, and the description covers scope, the empty-query behavior, and part of the return payload. The only meaningful gap is how results differ from the sibling MRLs tool.

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?

With a single parameter and 100% schema description coverage, the schema already says 'Drug name or fragment. Omit to list all.' The description restates the omit-to-list behavior and adds no syntax, matching, or casing details, so the baseline of 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 verb pair (list/search) and a well-scoped resource: veterinary drugs with Codex-adopted maximum residue limits in animal-derived food. It also names the drug classes covered (antibiotics, antiparasitics, growth promoters). It does not distinguish this from the sibling codex_vetdrug_mrls, which likely returns the residue limits themselves, so the agent must infer the split.

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?

There is clear guidance on parameter usage: omit the query to list everything, supply a name/fragment to search. There is no guidance on when to choose this tool over codex_vetdrug_mrls or codex_commodity_search, so the selection decision against the nearest sibling is left implicit.

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.