Skip to main content
Glama
nohosa001-pixel

EUDR Compliance & TRACES-NT Agent

eudr_arbitrate_agent_escrow

Arbitrates escrow disputes by checking Copernicus satellite data: post-2020 deforestation refunds the buyer; deforestation-free funds release to the seller.

Instructions

Executes deterministic autonomous dispute arbitration using Copernicus satellite telemetry. If deforestation is detected post-2020: 100% refund to Buyer Agent; if deforestation-free: released to Seller Agent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
plotsNoProduction plots for satellite radar arbitration.
reasonYesDispute claim / cause.
escrow_idYesUnique Escrow ID under dispute.
initiator_agent_idYesAgent initiating dispute.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the core behavioral outcome: post-2020 deforestation triggers a 100% refund to the Buyer Agent, while deforestation-free status releases funds to the Seller Agent. However, it omits authorization requirements, irreversibility, escrow state changes, and edge-case handling.

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 two tightly written sentences with no wasted words. The purpose and conditional outcomes are front-loaded, making it easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex financial arbitration tool with no annotations and no output schema, the description covers the central decision logic and payout outcomes but leaves gaps around caller permissions, preconditions, and return behavior. It is adequate but not fully complete.

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 four parameters. The description adds only contextual meaning by linking the process to Copernicus satellite telemetry, but it does not provide additional syntax, format, or dependency details beyond the schema.

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 and resource: deterministic autonomous dispute arbitration for an agent escrow. It clearly distinguishes the tool from generic escrow release siblings by its arbitration logic, though it does not explicitly name alternative tools.

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?

The description implies usage during a dispute and gives the decision rule based on post-2020 deforestation, but it does not state when to choose this tool over related siblings such as eudr_auto_slash_disputed_escrow or eudr_release_agent_escrow. No exclusions or prerequisites are provided.

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