Skip to main content
Glama
Sign In

Malaysia Land Lots & Local Plan Zoning

by io.github.BumiAtlas
OverviewDiscussionsAdmin

Get Malaysian lot

MY_lot_get
Read-onlyIdempotent

One Malaysian lot by UPI (id from MY_lot_search): negeri, daerah, mukim, seksyen and lot, keluasan (area recorded by JUPEM, m²), and zona, the local-plan zones covering it, largest share first: gunatanah (land use, Malay) with gunatanahEn (English), status (Sediada existing, Komited committed, Cadangan proposed) and share of the lot (0–1). Zones covering under 5% of the lot are left out, since zone and lot boundaries come from different surveys; empty zona means no local plan is loaded there. Set include_geometry for the boundary as GeoJSON.

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": {
      "id": "<id>"
    },
    "name": "MY_lot_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUPI, e.g. 1601400113193
include_geometryNoInclude the boundary as a GeoJSON MultiPolygon

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Although annotations already establish a safe read-only lookup, the description adds substantial domain-specific behavior: the 5% zone-share cutoff, the meaning of empty zona, the status values, and the share range. These are output semantics an agent would not infer from the annotations or schema alone.

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 description is front-loaded with the core lookup purpose and then efficiently details return fields and caveats. Despite being dense, every clause contributes to understanding what the tool returns and how zones are represented.

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?

There is no output schema, so the description carries the burden of explaining return content, and it does so thoroughly: lot identifiers, area units, zone ordering and cutoff, land-use fields, status values, share range, and geometry opt-in. Nothing essential for correct invocation appears missing.

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 both parameters are already documented. The description adds the useful source for id (MY_lot_search) and repeats that include_geometry returns the boundary as GeoJSON, but does not add much beyond the schema.

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: retrieving one Malaysian lot by UPI. It explicitly ties the id to MY_lot_search, which clearly differentiates it from the sibling search tool and from MY_lot_image or MY_zoning_get.

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?

It gives a clear usage path by saying the id comes from MY_lot_search and that this returns one lot rather than a list. It does not explicitly exclude or compare against MY_zoning_get or MY_lot_image, so it lacks full alternative guidance.

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

All Malaysia Land Lots & Local Plan Zoning 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