Skip to main content
Glama

Find a lot

mml_find_lot
Read-onlyIdempotent

Finds the land lot for an address, lot/plan, UK postcode, INSPIRE ID or coordinates. Returns the lot's MapMyLot id (row_id), lot/plan, area, perimeter, a point inside it, its outline as GeoJSON, a link to view it on mapmylot.com, and the data sources. In hosts that show apps the lot is also drawn on a map. Each new lot counts toward the account's daily MapMyLot lookups. Requires a free MapMyLot account.

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

Input Schema

NameRequiredDescriptionDefault
queryYesA street address, a lot/plan (QLD and NSW, e.g. 2/RP213261 or Lot 2 DP236756), a UK postcode, 'INSPIRE ID <number>' (England and Wales), or decimal coordinates 'lat, lon'

Output Schema

NameRequiredDescriptionDefault
bboxYes[min_lon, min_lat, max_lon, max_lat]
pointYes[lat, lon] of a point inside the lot
row_idYesThis lot's MapMyLot id
addressNoStreet address inside the lot, where known
area_m2No
sourcesYes
boundaryNoThe lot's outline as a GeoJSON Polygon or MultiPolygon in WGS84 (lon, lat), simplified for display; null when unavailable
localityNo
lot_planNoLot and plan as a person reads it, where the source has one
view_urlYesLink that opens this lot on mapmylot.com
area_nameYes
parcel_idYes
matched_byYes
perimeter_mNo
data_vintageNo
jurisdictionYes
lookups_leftNoFree accounts: lots left today (shared with mapmylot.com)
matched_textNoThe lot/plan or address the query resolved to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description usefully adds non-obvious operational context: an account is required and each new lot consumes a daily lookup quota. It does not clarify caching on repeat queries, rate limits beyond the daily counter, or failure behaviour for ambiguous addresses.

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?

Three sentences, front-loaded with purpose, then outputs, then cost/account prerequisites. The return-value enumeration is somewhat redundant given an output schema exists, but nothing is filler.

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?

With an output schema present, the return-field list is optional, yet the description still covers the key operational prerequisites (account, quota) and the host-dependent map rendering. The main gap is what happens on ambiguous or non-matching queries, which matters for a geocoding lookup.

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 the query parameter already documents each accepted format with examples. The description's first sentence repeats that same list, adding no format, escaping or ambiguity-resolution detail beyond the schema, so the baseline of 3 applies.

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?

Opens with a specific verb and resource ('Finds the land lot') and enumerates every accepted identifier type (address, lot/plan, UK postcode, INSPIRE ID, coordinates), so the tool's role as a free-form lookup is unambiguous. It stops short of naming a sibling it is not (e.g. mml_lot_facts), so differentiation is inferred from the query-style input rather than stated.

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 list of accepted query forms implies when the tool applies, and the note that it returns a row_id hints that it is the entry point for id-based tools. There is no explicit when-not guidance and no named alternative for cases such as already holding a row_id.

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