Skip to main content
Glama

eudr_polygon_geolocation_verifier

Read-onlyIdempotent

[EUDR polygon geolocation & 6-decimal coordinate topology verifier. Pure calculation, read-only, side-effect free]. Verifies geographic coordinates of plots of land under Regulation (EU) 2023/1115 Article 9(1)(d), auditing mandatory 6-decimal precision, closure, coordinate bounding, and enforcing polygon requirements for plots >= 4 hectares. Usage: Pass plot ID, declared area in hectares, and latitude/longitude coordinates to audit EUDR spatial compliance. Returns: JSON object with { plotOfLandIdentifier: string, declaredAreaHectares: number, calculatedAreaHectares: number, geometryType: string, coordinatePrecisionCheck: object, topologyCheck: object, statutoryComplianceVerdict: string, discrepancies: array }.

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": {
      "plotOfLandIdentifier": "<plotOfLandIdentifier>",
      "declaredAreaHectares": "<declaredAreaHectares>",
      "coordinates": "<coordinates>"
    },
    "name": "eudr_polygon_geolocation_verifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
coordinatesYesCoordinates array: single point for plots < 4 ha, or closed polygon vertices (first === last) for plots >= 4 ha
declaredAreaHectaresYesDeclared surface area of the plot of land in hectares
plotOfLandIdentifierYesCadastral parcel identifier or internal farm plot code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description adds that this is pure calculation and side-effect free. It further discloses the specific checks performed and the return fields, giving the agent substantial behavioral context beyond the annotations.

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 definition is front-loaded with the tool's identity and safety profile, followed by usage and return structure. Every section is relevant, and the return schema is especially useful because no output schema is provided.

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

Completeness5/5

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

Given the tool's regulatory complexity and the absence of an output schema, the description is complete enough for correct invocation. It covers the regulation, required inputs, audit checks, and the shape of the returned JSON.

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 three parameters in detail. The description reinforces the 6-decimal precision, closure, bounding, and polygon requirements, but it adds little parameter meaning beyond what the schema already states.

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 and resource: it verifies EUDR plot geolocation and 6-decimal coordinate topology. It also names the relevant regulation and audit dimensions, making it clearly distinguishable from sibling compliance tools such as the due diligence statement validator.

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' sentence gives clear context: pass plot ID, declared area, and coordinates to audit EUDR spatial compliance. It does not explicitly state when not to use this tool or name an alternative, but the intended context is clear.

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