Skip to main content
Glama
nohosa001-pixel

EUDR Compliance & TRACES-NT Agent

by nohosa001-pixel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

eudr_benchmark_country

Evaluate EUDR Article 29 country risk tiers to determine Article 13 simplified due diligence eligibility and official EU customs audit rates (1%, 3%, 9%).

Instructions

Evaluates EUDR Article 29 country benchmarking risk tier (Low, Standard, High) and determines Article 13 simplified due diligence eligibility with official EU customs audit rates (1%, 3%, 9%).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
country_codeYesISO 3166-1 alpha-2 country code of production origin (e.g. 'DE', 'ID', 'BR', 'MM', 'KP').
suspected_mixingNoWhether bulk mixing with unknown or high-risk origin plots is suspected.
suspected_circumventionNoWhether transshipment laundering or regulatory circumvention is suspected.
corruption_index_overrideNoOptional CPI score override (0-100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

Without annotations, the description must carry the full behavioral burden. It discloses that the tool evaluates and determines eligibility, and mentions official audit rates, but it does not clarify whether the operation is read-only, whether it has side effects, or what permissions are required. The behavioral context is adequate but incomplete.

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?

The description is a single, information-dense sentence that front-loads the core purpose and includes specific regulatory references and output values. Every part earns its place with no redundancy.

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?

Given no annotations and no output schema, the description is fairly complete: it explains the evaluation, the output tiers, and audit rates. It could benefit from more detail on the return format or behavioral traits, but it covers the essential information an agent needs to invoke the tool 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 all parameters thoroughly. The description adds no parameter-specific semantics beyond what is in the schema, so the baseline of 3 is appropriate.

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?

The description states a specific verb (Evaluates, determines) and resource (EUDR Article 29 country benchmarking risk tier, Article 13 simplified due diligence eligibility). It clearly distinguishes this tool from siblings by focusing on country-level risk tier assessment and customs audit rates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool versus alternatives. It explains what the tool does but does not mention any prerequisites, conditions, or sibling tools that might be more appropriate in certain contexts.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools