Skip to main content
Glama

MapMyLot coverage

mml_coverage
Read-onlyIdempotent

Lists the areas MapMyLot covers, what each accepts (lot/plan, street address, postcode, coordinates), which planning and hazard layers are loaded, and the daily limits for each plan. Works without sign-in.

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_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoOptional filter: AU, NZ, CA or UK, or an area code such as qld

Output Schema

NameRequiredDescriptionDefault
areasYes
limitsYes
sign_inYes
not_coveredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description still adds real context beyond that: it works without authentication, and it discloses per-plan daily limits, which is exactly the kind of rate-limit information annotations cannot express.

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 the verb and resource, then a compact parenthetical listing accepted input formats, plus one short sentence on sign-in. Dense but every clause carries content; only the parenthetical slightly compresses into a long single sentence.

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 need not explain return values, and annotations cover the safety profile, so the remaining burdens are auth and limits, both addressed. The only gap is that the country filter's role in scoping the coverage list 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 description coverage is 100% and the single optional country parameter is fully documented in the schema, including example values (AU, NZ, CA, UK, qld). The description never mentions the country filter, so it adds no meaning beyond the schema; baseline 3 applies.

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 ("Lists") and a precise resource (the areas MapMyLot covers), then enumerates what the answer contains: accepted location formats, loaded planning and hazard layers, and per-plan daily limits. This is clearly a discovery/metadata tool and is distinguishable from siblings like mml_find_lot and mml_lot_facts without opening any 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?

"Works without sign-in" signals the tool is usable pre-auth and is a useful hint about when it applies, but there is no explicit guidance such as calling this first to discover supported areas before invoking mml_find_lot, and no when-not-to-use conditions. Usage is implied rather than stated.

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