Skip to main content
Glama

Bhumi MCP: Data Tanah ATR/BPN, RDTR OSS, HGU & Konsesi

by io.github.BumiAtlas
OverviewDiscussionsAdmin

Get parcel

Parcel_get
Read-onlyIdempotent

Full record of one parcel by id: certificate number, NIB, right type, declared area (luas) next to the area of the mapped polygon (luasHitung) and their difference in percent, year, survey method (alatukur), mapping accuracy (akurasibidang, unit unknown), the village, perimeter and side lengths in metres, and center, a [longitude, latitude] point inside the parcel. zona lists the RDTR zoning sub-zones covering the parcel (kodzon/namzon zone, kodszn/namszn sub-zone, share of the parcel 0–1), largest first; empty where no detailed spatial plan is loaded. znt lists the land value zones (Zona Nilai Tanah) covering the parcel from each land office's latest year: kelas 1–9 stands for a range in Rp/m² (1 < 100k, 2 100k–200k, 3 200k–500k, 4 500k–1M, 5 1M–2M, 6 2M–5M, 7 5M–10M, 8 10M–20M, 9 > 20M), with tahun and share of the parcel; empty where no ZNT is loaded. banjir lists the BNPB flood hazard classes covering the parcel (kelas 1 rendah/low, 2 sedang/medium, 3 tinggi/high, with share of the parcel), largest first; empty means BNPB maps no flood hazard there. The hazard map has 100 m cells, so it rates the neighbourhood rather than the exact plot. A large area difference can point to a mapping error or an outdated certificate. nilai is almost always empty in the source. Set include_geometry for the boundary as GeoJSON.

Input Schema

NameRequiredDescriptionDefault
idYesParcel id from Parcel_search
include_geometryNoInclude the boundary as a GeoJSON MultiPolygon

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already establish safe read-only/idempotent behavior. The description adds substantial beyond that: empty-case meanings for zona/znt/banjir, ZNT class ranges, the 100m flood-cell caveat, interpretation of area difference, and that nilai is usually empty.

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-loaded with the core purpose and dense with field semantics because there is no output schema. It is long and one paragraph, but most clauses earn place by explaining return fields; minor structural issue.

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?

No output schema, so description carries return-value burden; it comprehensively explains fields, empty states, and caveats. For a read-only getter with annotation coverage, it is complete enough.

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% and both parameters are already documented in schema. Description reinforces id scoping and include_geometry but adds little syntax/semantic detail beyond schema; baseline 3.

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 opens with 'Full record of one parcel by id', which states the resource and scope precisely and implies retrieval. It does not explicitly name Parcel_search or another sibling as the alternative, so it is clear but lacks explicit sibling differentiation.

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?

It implies use when you have a parcel id and want the full record, and notes include_geometry for boundary retrieval. It does not state when to use this versus Parcel_search/Parcel_overlaps or any prerequisites/exclusions.

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

All Bhumi MCP: Data Tanah ATR/BPN, RDTR OSS, HGU & Konsesi toolsInspect
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.

Resources