Skip to main content
Glama
Sign In

Malaysia Land Lots & Local Plan Zoning

by io.github.BumiAtlas
OverviewDiscussionsAdmin

Search Malaysian lots

MY_lot_search
Read-onlyIdempotent

Find Malaysian land lots (JUPEM cadastre) by UPI, lot number or location. query takes a UPI (e.g. 1601400113193; dots, dashes and spaces allowed), a lot number ('Lot 3193', 'PT 1234') with negeri and optionally daerah, mukim and seksyen codes to narrow it, or coordinates as 'latitude, longitude' (e.g. 2.9264, 101.6964). With coordinates it returns the lots containing the point (distance 0), then the nearest within radius metres, closest first. To search an address, geocode it first; a radius of 25–100 m helps with geocoded points. Lots are only loaded for some states so far, so no result may just mean the state isn't loaded. Each lot has id (the UPI), negeri and negeriName, daerah, mukim (and mukimName where known), seksyen, lot, keluasan (m²) and bbox. Use MY_lot_get with an id for zoning and the boundary.

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": {
      "query": "<query>"
    },
    "name": "MY_lot_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results
mukimNo2-digit mukim code, to narrow a lot number
queryYesUPI, lot number ('Lot 3193'), or 'latitude, longitude'
daerahNo2-digit district code, to narrow a lot number
negeriNoState code (01 Johor … 16 W.P. Putrajaya) or name, to narrow a lot number
radiusNoSearch radius in metres around coordinates
seksyenNo3-digit section code, to narrow a lot number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent safety, but the description adds context they cannot: coordinate searches return containing lots (distance 0) first, then nearest within radius, closest first, and lots are only loaded for some states so an empty result may reflect missing coverage rather than a true negative.

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 purpose, then modes, then the coverage caveat, then field list — a sensible order with no filler. The return-field enumeration is dense but justified given there is no output schema.

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?

With no output schema, the description supplies the returned fields (id, negeri/negeriName, daerah, mukim, seksyen, lot, keluasan, bbox), ordering behavior, radius guidance, and the partial-coverage caveat — everything needed to call and interpret this tool correctly.

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 exceeds it by explaining the UPI syntax with punctuation tolerance, lot-number formats ('Lot 3193', 'PT 1234'), coordinate format, radius semantics, and that negeri/daerah/mukim/seksyen exist to narrow a lot-number search.

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 and resource ('Find Malaysian land lots (JUPEM cadastre)') and immediately enumerates the three query modes: UPI, lot number, coordinates. It also distinguishes itself from the sibling MY_lot_get, which is named as the follow-up for zoning and boundary detail.

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?

Explicit routing: use a UPI, a lot number with negeri plus optional daerah/mukim/seksyen, or coordinates. It also tells the agent to geocode an address first and suggests a 25–100 m radius for geocoded points, and redirects to MY_lot_get for zoning/boundary — leaving little to inference.

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