Skip to main content
Glama

eudr_due_diligence_statement_validator

Read-onlyIdempotent

[EUDR deforestation due diligence statement (DDS) TRACES NT validator. Statutory audit, read-only, side-effect free]. Audits and validates operator Due Diligence Statements under Regulation (EU) 2023/1115 (EUDR) Articles 4, 8, and 9, verifying regulated commodity HS codes (Annex I), country risk tier, deforestation-free cutoff (31 Dec 2020), and legality of production. Usage: Pass operator, commodity code, and compliance declarations to verify readiness for TRACES NT submission. Returns: JSON object with { statementReference: string, operatorName: string, commodityCategory: string, isRegulatedCommodity: boolean, countryRiskTier: string, simplifiedDueDiligenceApplicable: boolean, cutoffDateCompliant: boolean, isDueDiligenceComplete: boolean, readinessVerdict: string, deficiencies: array, tracesPayloadPreview: object }.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operatorName": "<operatorName>",
      "operatorVatOrEori": "<operatorVatOrEori>",
      "operatorCountryIso2": "<operatorCountryIso2>",
      "activityType": "<activityType>",
      "commodityCodeHs": "<commodityCodeHs>",
      "commodityDescription": "<commodityDescription>",
      "countryOfProductionIso2": "<countryOfProductionIso2>",
      "productionDateFromIso": "<productionDateFromIso>",
      "productionDateToIso": "<productionDateToIso>",
      "hasPolygonGeolocationProof": "<hasPolygonGeolocationProof>",
      "isProducedOnLegallyOwnedLand": "<isProducedOnLegallyOwnedLand>",
      "deforestationFreeCutoffVerifiedPost2020": "<deforestationFreeCutoffVerifiedPost2020>",
      "totalQuantityKgOrUnits": "<totalQuantityKgOrUnits>"
    },
    "name": "eudr_due_diligence_statement_validator"
  }
}

Input Schema

NameRequiredDescriptionDefault
activityTypeYesNature of commercial transaction under EUDR Art. 3
operatorNameYesLegal name of the operator or trader placing commodities on the EU market
commodityCodeHsYesHarmonized System (HS) tariff code (e.g. 1801 for cocoa, 0901 for coffee, 4407 for wood, 1201 for soya)
operatorVatOrEoriYesOperator EORI number or national VAT tax identifier
operatorCountryIso2Yes2-letter ISO country code of operator establishment
productionDateToIsoYesLatest production/harvest date (YYYY-MM-DD)
commodityDescriptionYesCommercial trade description of the commodity/product
productionDateFromIsoYesEarliest production/harvest date (YYYY-MM-DD)
totalQuantityKgOrUnitsYesNet mass in kilograms or supplementary volume units declared
countryOfProductionIso2Yes2-letter ISO country code where the commodity was produced/harvested
hasPolygonGeolocationProofYesWhether geographic coordinates of all plots of land are documented (Art. 9(1)(d))
isProducedOnLegallyOwnedLandYesWhether production complied with relevant local legislation on land tenure, labor, and environment (Art. 3(b))
deforestationFreeCutoffVerifiedPost2020YesVerification that commodity was produced on land that was not subject to deforestation or forest degradation after 31 December 2020

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces this with 'Statutory audit, read-only, side-effect free', which signals no external state is mutated. It also goes beyond annotations by spelling out the full response envelope (readinessVerdict, deficiencies array, tracesPayloadPreview), giving the agent visibility into what a validation run yields.

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?

The bracketed tag, purpose, usage, and returns blocks are cleanly separated and front-loaded, so an agent gets the purpose in the first sentence. The returns block is long but substitutes for the missing output schema, so it earns its space; the only mild redundancy is restating 'read-only, side-effect free' already covered by annotations.

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?

For a 13-required-parameter statutory validator with no output schema, the definition covers both invocation inputs (via the 100% documented schema) and the return shape. It does not explain how readinessVerdict or countryRiskTier are derived, which would be the remaining gap for an agent interpreting results.

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 every one of the 13 required parameters is already documented in the schema. The description adds only framing context (that HS codes are Annex I regulated commodities and that the cutoff date is 31 Dec 2020) rather than per-parameter meaning, so the baseline of 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 ('Audits and validates operator Due Diligence Statements') and pins the regulatory basis to Regulation (EU) 2023/1115 Articles 4, 8, and 9. It enumerates the concrete checks performed (Annex I HS codes, country risk tier, 31 Dec 2020 cutoff, legality), which distinguishes it from siblings like eudr_polygon_geolocation_verifier or taric_hs_validator without needing their schemas.

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?

The 'Usage' line gives a clear context: pass operator, commodity code, and compliance declarations to verify readiness for TRACES NT submission. It does not, however, state exclusions or say what to do when a submission is a non-EUDR good, nor point at sibling tools for sub-checks such as polygon verification.

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.

Resources