Skip to main content
Glama

Eu Pesticide Substance

eu_pesticide_substance
Read-onlyIdempotent

EU approval record for one pesticide (plant-protection) active substance from the European Commission EU Pesticides Database: approval status (Approved / Not approved / Pending), an explicit approval_state that flags an Approved entry whose expiry date has already passed, first-approval date, expiry date, the governing Commission regulations and directives (links to EUR-Lex; this is how to see whether and under which implementing regulation an approval was renewed or extended), rapporteur member state, candidate-for-substitution and low-risk flags, ADI / ARfD / AOEL reference values, CLP classification, national authorisations and MRL residue definitions. Look up by name (exact, then partial), CAS number or substance id. Returns data_as_of with every answer. Keyless.

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": {
      "name": "dimethachlor"
    },
    "name": "eu_pesticide_substance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoEU Pesticides Database substance id.
casNoCAS number, e.g. "50563-36-5".
nameNoActive substance name, e.g. "dimethachlor", "glyphosate", "chlorpyrifos". Exact match preferred; otherwise partial matches are listed.

Output Schema

NameRequiredDescriptionDefault
matchesNo
substanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 covered. The description adds genuine non-annotation context: keyless access (no auth setup), 'Returns data_as_of with every answer' (freshness signalling), and the exact-then-partial name fallback. It still omits any mention of rate limits, truncation, or what happens when no match is found.

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?

Purpose and source are front-loaded, followed by scope, capability and lookup modes. The long enumerative field list is dense but each item carries selection value; it could be trimmed somewhat since an output schema already exists.

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?

An agent knows the source, the grain (one substance), the lookup keys, that access is keyless, and that results carry data_as_of. With an output schema present, the exhaustive return-field enumeration is partly redundant, and no-match / ambiguity behaviour is unstated, but nothing essential for correct invocation is missing.

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%, so all three parameters (id, cas, name) are already documented in the schema, including the exact-then-partial name behaviour. The description restates the same lookup modes without adding syntax, format, or precedence rules beyond what the schema provides, so the baseline 3 applies.

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: 'EU approval record for one pesticide (plant-protection) active substance' from a named authoritative source. The singular focus plus the full field inventory makes it distinguishable from the sibling eu_pesticides_list even though the sibling is not named explicitly.

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 concrete lookup modes: 'Look up by name (exact, then partial), CAS number or substance id', which tells an agent which parameter path to take. It never says when to prefer eu_pesticides_list (bulk listing) over this single-record lookup, so the sibling boundary 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.