Skip to main content
Glama

Compare lots

mml_compare_lots
Read-onlyIdempotent

Returns side-by-side facts for 2 to 10 lots: one row per lot with the same facts as the lot facts result, or that lot's error. Rows stay in the order given, or follow a requested sort (by area, frontage, layers found, constraint score and so on); sorted_by states the order used. The result is facts only, with no ranking of which lot is better. Each new lot counts toward the day's lookups. Requires a MapMyLot Pro plan.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mml_compare_lots"
  }
}

Input Schema

NameRequiredDescriptionDefault
lotsNo2 to 10 lots: row_ids returned by the lot search, or addresses, lot/plans or coordinates
sortNoThe facts the user asked to order the rows by, in turn, each with a direction, for example fewest layers_present first, then largest area_m2. Without it, the rows stay in the order given
savedNoCompares the account's saved lots instead (up to 10, newest first)

Output Schema

NameRequiredDescriptionDefault
noteYes
rowsYes
sorted_byYesThe order the rows are in

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare a safe read, so the description correctly spends its words elsewhere: quota consumption ('Each new lot counts toward the day's lookups'), an entitlement gate ('Requires a MapMyLot Pro plan'), per-row error handling, and an explicit 'no ranking' caveat that prevents the agent from over-reading the output. That is meaningful behavior beyond the structured fields.

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?

Purpose is front-loaded and each sentence carries distinct information: row shape, ordering, the no-ranking caveat, quota, entitlement. Slightly dense at five sentences, 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, return values need no prose, and the description still covers ordering, error rows, quota and plan gating. The one gap is the `saved`-mode branch, which is left entirely to the schema.

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%, so the schema already documents `lots`, `sort` keys and `saved`. The description restates the 2-to-10 bound and illustrates sort ordering ('by area, frontage, layers found, constraint score'), which is mild added meaning, but it never mentions the `saved` mode switch that changes what `lots` means.

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 ('Returns side-by-side facts for 2 to 10 lots') plus the row shape ('one row per lot with the same facts as the lot facts result, or that lot's error'). It anchors itself against the sibling mml_lot_facts, so an agent can tell comparison from single-lot facts without opening a schema.

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 rather than stated: the 2-to-10 constraint and the reference to 'the lot facts result' signal this is the multi-lot counterpart of mml_lot_facts, but there is no explicit 'use X instead when Y' routing and no mention of the `saved` mode as an alternative path. Adequate but leaves the agent to infer the boundary.

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