Skip to main content
Glama
Sign In

Pakistan Land Parcels & Khasra Lookup (پنجاب اراضی)

by io.github.BumiAtlas
OverviewDiscussionsAdmin

Search Punjab (Pakistan) land parcels

PK_parcel_search
Read-onlyIdempotent

Find urban Punjab parcels (PULSE development-authority data) by parcel code, society name, or location, with each parcel's whole record. query takes a parcel code ('TXL-TEH-00C-000-0157-0000'; a prefix like 'MDT-TNS' lists that tehsil's or mouza's parcels), a housing society name or part of one ('DHA', 'Millat Town'), or coordinates as 'latitude, longitude' (e.g. 31.4726, 74.2728). With coordinates it returns parcels containing the point (distance 0), then the nearest within radius metres, closest first. Society and prefix searches list parcels paged with offset. Each parcel has id, uniParco, khasra (plot number), plotNo, block, sector, phase, society, source (which authority's layer), landuse, landuseSub, plotSize, area and mapArea (m²), anomaly (PULSE's data-quality flag), district, tehsil, division and bbox. Set include_geometry for each boundary as GeoJSON (keep limit small). Use PK_parcel_image to see a parcel and its neighbours.

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": "PK_parcel_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results
queryYesparcel code or prefix ('TXL-TEH-00C-000-0157-0000', 'MDT-TNS'), society name ('DHA'), or 'latitude, longitude'
offsetNoSkip this many parcels of a society or code prefix, to page through them
radiusNoSearch radius in metres around coordinates
include_geometryNoInclude each boundary as a GeoJSON MultiPolygon

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so safety is covered; the description adds genuinely new behavior: coordinate searches return containing parcels (distance 0) first, then nearest within radius sorted closest-first, while society/prefix searches page with offset. It omits any auth, rate-limit or empty-result behavior, and the offset/limit interaction across modes is only partly spelled out.

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 and query modes, and every clause carries information (field list compensates for the missing output schema). It is a single dense paragraph, however, and the long field enumeration could be broken out or trimmed for faster scanning.

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 takes on the burden of describing returned fields (id, uniParco, khasra, plotNo, block, society, landuse, area, anomaly, bbox), and it does so thoroughly. Paging, geometry payload size and the sibling tool for imagery are all covered, so nothing needed to call it correctly is missing.

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 description coverage is 100%, so baseline is 3; the description still adds meaning by giving concrete query formats, explaining that radius only applies to coordinate searches and drives ordering, and clarifying that offset pages society and prefix listings. The include_geometry caveat also adds practical semantics beyond the schema's one-line description.

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 urban Punjab parcels") plus the data provenance (PULSE development-authority layers). It explicitly distinguishes itself from the sole sibling by directing image/neighbour viewing to PK_parcel_image, so an agent can route without opening either schema.

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?

Enumerates the three accepted query modes and the condition that selects each: parcel code or prefix for a tehsil/mouza listing, society name for a name listing, coordinates for a spatial search. It also gives a usage caveat ("keep limit small" with include_geometry) and names the alternative tool for visual inspection.

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

All Pakistan Land Parcels & Khasra Lookup (پنجاب اراضی) 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