Skip to main content
Glama

Lot facts

mml_lot_facts
Read-onlyIdempotent

Returns facts about a lot by its row_id: area, perimeter, frontage, traditional custodians, a 0-100 constraint score, each planning and hazard layer checked on the lot (present or not, value, share of the lot), the unconstrained area, how its size compares with the suburb, distances to the coast, parks, water and transmission lines, elevation, and whether boundary files exist. A lot whose report the account bought has every answer, as on Pro. Layers checked on the lot but not included on the account's plan are listed in locked_layers; a locked layer is not absent. Spends no lookup.

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": {
      "row_id": "<row_id>"
    },
    "name": "mml_lot_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
row_idYesThe lot's row_id, as returned by the lot search or in the list of purchased reports

Output Schema

NameRequiredDescriptionDefault
lotYesIdentity, area, perimeter, frontage, custodians and data date
tierYes
filesYesWhether boundary files (DXF, KML, GeoJSON) exist here and this account can download them on the site
scoreYes0-100 constraint score (higher is less constrained) and how many answers are withheld
layersYesLayers answered for this account: present or not, value, coverage
nearbyYesDistances to the coast, parks, water and transmission lines
reportYes
row_idYes
suburbNoLot count and median lot area in the suburb
sourcesYes
view_urlYes
elevationNo
percentileNo
locked_lineNoWhich answers are locked and how they are unlocked; present only when answers are locked
unlocked_byNoWhy this lot's answers are all unlocked: the account's Pro plan, or the report the account bought for this lot (other lots stay at the account's plan)
locked_layersYes
unconstrainedNoArea left after exclusionary layers; locked unless Pro or the report for this lot
more_present_countYesHow many locked layers apply to this lot
note_for_assistantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses plan-dependent behavior ('A lot whose report the account bought has every answer, as on Pro') and the crucial nuance that entries in locked_layers mean not-included rather than absent. It also states the call spends no lookup, which is quota-relevant context. Error behavior for an invalid row_id is not covered, and the return shape is left to the output schema.

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?

It is front-loaded with the core action, and each following clause carries real information (returned fields, locked-layer semantics, cost). The long comma-separated field enumeration is dense but not padded; a bulleted or grouped structure would read faster, but nothing is wasted.

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 description does not need to explain return values, yet it helpfully flags the account-tier and locked_layers behavior an agent would otherwise misread as missing data. The main remaining gap is what happens on an unknown row_id or a lot the account has not purchased.

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?

There is a single required parameter with 100% schema description coverage, including where row_id comes from ('as returned by the lot search or in the list of purchased reports'). The description's 'by its row_id' only restates the schema, adding no format or validation detail beyond it, so the baseline 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?

The description opens with a specific verb and resource ('Returns facts about a lot by its row_id') and then enumerates the concrete data returned — geometry, constraint score, per-layer results, distances, elevation. An agent can tell this is a fact-lookup tool, though it never names a sibling (e.g. mml_find_lot or mml_build_facts) to differentiate itself.

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?

Usage is only implied: you must already have a row_id from the lot search or purchased-report list. 'Spends no lookup' hints that calling it is cheap, but there is no explicit when-to-use/when-not guidance against siblings such as mml_find_lot or mml_compare_lots.

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