Skip to main content
Glama

Lot facts for building questions

mml_build_facts
Read-onlyIdempotent

Returns the facts about a lot that bear on building: area, frontage, zone (where zoning is loaded), planning and hazard constraints, unconstrained area, and slope and fall. The result is facts only, with no ruling on what can be built, and carries a caveat that the council decides. 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_build_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
zoneYes
slopeYesElevation range, fall and average slope; locked unless Pro or the report for this lot; not_offered where no elevation data covers the lot
caveatYes
row_idYes
area_m2No
sourcesYes
view_urlYes
frontage_mNo
constraintsYesLayers answered for this account
locked_lineNo
perimeter_mNo
frontage_textNo
locked_layersYes
unconstrainedNo
open_frontage_mNo
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?

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real value beyond them: it discloses the no-ruling caveat, that the council is the decision authority, that results are facts only, and that it 'spends no lookup' — a cost/credit signal not derivable from annotations.

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 tight sentences with the field list front-loaded and no padding. 'Spends no lookup' is terse to the point of being cryptic, costing a little clarity, but nothing is redundant.

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?

An output schema exists, so return structure need not be restated, and the description nonetheless previews the returned fields and the accompanying caveat. Combined with full schema coverage and rich annotations, the agent has what it needs, with only the sibling differentiation left implicit.

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 parameter with 100% schema description coverage, which already explains row_id and where to obtain it. The description adds nothing further about the identifier's semantics, 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 uses a specific verb (returns) plus resource (facts about a lot) and enumerates the exact fields returned: area, frontage, zone, planning and hazard constraints, unconstrained area, slope and fall. The building-specific framing distinguishes it conceptually from the more generic-sounding mml_lot_facts, but the sibling is never named, so the agent must infer the split.

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 implied by the title and the phrase 'facts that bear on building,' so an agent can infer this is for buildability questions rather than general lot data. However, there is no explicit when-to-use vs mml_lot_facts or when-not guidance, and the nearest alternative is left unaddressed.

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