eudr

Set a farm's boundary

eudr_set_farm_boundary

Destructive

Set the boundary of a farm already in the record, as boundary (GeoJSON Polygon or MultiPolygon) or as fields to join into one farm (see eudr_create_farm). It becomes the farm's confirmed boundary, recorded as set by this agent credential, and what follows runs at once: the country from where the land lies, the forest record warmed, the land check. This writes to the organisation's record, and REPLACES any boundary the farm already had: the previous outline stops being the farm's boundary, and because the boundary decides which land is checked, the compliance answers and the area derived from it change with it. The superseded outline is kept in the farm's history and can be read back, but this call does not undo on its own — confirm with the user before overwriting a boundary somebody else set.

Input Schema

Name	Required	Description
`fields`	No	Several field outlines to join into one farm, as GeoJSON Polygons. Give this or `boundary`.
`join_m`	No	How far apart two field outlines may be and still count as one farm, in metres each way. Default 3.
`farm_id`	Yes	The farm whose boundary this is, as `eudr_create_farm` or `eudr_list_farms` returned it.
`boundary`	No	The outline, as a GeoJSON Polygon or MultiPolygon, longitude first. Give this or `fields`.

Output Schema

Name	Required	Description	Default
`then`	No
`area_ha`	Yes
`farm_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 15, 2026

addedInput schema / properties / boundary / description

Added value: +"The outline, as a GeoJSON Polygon or MultiPolygon, longitude first. Give this or `fields`."

addedInput schema / properties / farm_id / description

Added value: +"The farm whose boundary this is, as `eudr_create_farm` or `eudr_list_farms` returned it."

addedInput schema / properties / fields / description

Added value: +"Several field outlines to join into one farm, as GeoJSON Polygons. Give this or `boundary`."

addedInput schema / properties / join_m / description

Added value: +"How far apart two field outlines may be and still count as one farm, in metres each way. Default 3."

AddedSep 29, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description goes further by stating exactly what is destroyed (the previous outline stops being the boundary), what the effects are (compliance answers and area change), that the superseded outline is kept in history, and that the call does not undo on its own. This is rich 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core action and modes, then sequences consequences and warnings. Somewhat dense with subordinate clauses, but every sentence carries load. Not maximally tight but appropriate for the complexity.

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?

The tool has an output schema, so return values need not be explained. The description covers the mutation, its destructive effects, history retention, and a user-confirmation warning, which is complete for a destructive, non-idempotent tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds interpretation of 'boundary' vs 'fields' (GeoJSON Polygon/MultiPolygon, joining into one farm) that helps the agent understand the semantics, though it largely restates what the schema already documents.

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+resource ('set the boundary of a farm') and distinguishes the two input modes (boundary vs fields) that map to the siblings eudr_create_farm context. Differentiated from other tools by clarifying it acts on an existing farm in the record.

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

Usage Guidelines5/5

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

Explains the two modes of providing input, references eudr_create_farm for farm creation, and includes an explicit precondition ('confirm with the user before overwriting a boundary somebody else set'). This is when-to-use guidance with an exclusion/warning.

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

All eudr tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.