Skip to main content
Glama

Get Parcel Boundaries

get_boundaries

Get the outline of a cadastral parcel as GeoJSON and/or a [lat, lng] ring, plus its centroid and area, for mapping and GIS work. Accepts references from the same 31 codes as get_parcel except the United Kingdom, which is coordinates only.

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": {
      "reference": "<reference>"
    },
    "name": "get_boundaries"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoOptional country code. Omit to auto-detect from the reference format.
referenceYesOfficial cadastral reference

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully reveals the return shape (GeoJSON and/or ring, centroid, area) and one geographic constraint, but says nothing about ring closure/winding order, precision, failure behavior for unknown references, or whether lookup is billable or rate limited.

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?

Two tight sentences with the payload described first and the reference/UK caveat second; nothing is redundant. The second sentence is dense but still parses cleanly.

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 two-parameter lookup with no output schema and no annotations, the description covers what comes back and the main input constraint. Only error/empty-result behavior and geometry format details are absent, which are minor for this complexity level.

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, but the description adds genuine meaning: it explains why the country enum lacks GB (United Kingdom is coordinates only) and ties the accepted reference formats back to get_parcel's 31-code set. That context is not recoverable from the schema alone.

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?

States a specific verb and resource ('Get the outline of a cadastral parcel') and enumerates the exact payload: GeoJSON and/or a [lat, lng] ring, centroid and area. The contrast with get_parcel over the accepted reference codes further separates it from the sibling that returns parcel attributes.

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 phrase 'for mapping and GIS work' supplies an implied use case, and the UK exception ('coordinates only') tells the agent one case where reference lookup fails. But there is no explicit statement of when to prefer this over get_parcel or get_parcel_sigpac, and no prerequisites are given.

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