Skip to main content
Glama

Lot report link

mml_report_link
Idempotent

Returns a permanent link to the MapMyLot PDF report for a lot when the account has bought that report or has a Pro plan; otherwise how the report is obtained. With no row_id, lists the reports this account has bought. Spends no lookup.

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

Input Schema

NameRequiredDescriptionDefault
row_idNoThe lot's row_id, as returned by the lot search. Without it, the account's purchased reports are listed

Output Schema

NameRequiredDescriptionDefault
messageYes
reportsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already set readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds meaningful behavior beyond those hints: entitlement gating, fallback information when the report is not owned, the no-row_id listing behavior, and that it 'Spends no lookup.' It does not explain why readOnlyHint is false or detail side effects, but it does not contradict the 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?

The description is short and front-loads the primary return behavior before the no-row_id fallback. The phrasing 'otherwise how the report is obtained' and 'Spends no lookup' is slightly vague or awkward, but there is little wasted text.

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 one parameter, an output schema, and fully specified schema coverage, the description covers the main modes: link retrieval for a lot and listing purchased reports without row_id. Minor gaps remain around why readOnlyHint is false and the exact response when the account lacks entitlement, but the core behavior is complete.

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 row_id parameter already documents that omitting it lists the account's purchased reports. The description reinforces the no-row_id behavior but adds little semantic meaning beyond the schema, so the baseline of 3 is appropriate.

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?

The description uses a specific verb and resource: 'Returns a permanent link to the MapMyLot PDF report for a lot.' It also covers the no-row_id listing mode and entitlement conditions, making the tool's scope clear without needing sibling comparison.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context for when the tool applies: with a lot row_id and an owned or Pro-plan report, or without row_id to list purchased reports. It does not name sibling alternatives or explicit when-not cases, but the conditional usage is sufficiently explicit.

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