Skip to main content
Glama

Save a lot

mml_save_lot
Idempotent

Saves a lot to the account's saved lots on MapMyLot, with an optional note. Saving the same lot again changes nothing. Saved lots are removed on mapmylot.com. 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_save_lot"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoOptional short note to save with the lot
row_idYesThe lot's row_id, as returned by the lot search or in the list of purchased reports

Output Schema

NameRequiredDescriptionDefault
idNo
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false). The description adds information beyond them: the cost model ('Spends no lookup') and the fact that removal happens out-of-band on mapmylot.com rather than through a paired tool, which is the non-obvious behavioral detail an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the action, and each carries distinct information: the operation, the optional note, idempotency, out-of-band removal, and cost. Nothing is redundant padding.

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 and rich annotations, the description needn't explain return values, and it covers the remaining gaps an agent would worry about: cost, repeat-call behavior, and how saved lots are undone. Only the save-vs-watch distinction is left unaddressed.

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 row_id and label are already fully documented in the schema. The description only restates that the note is optional, adding no format, length, or sourcing detail beyond what the schema provides. Baseline 3 is appropriate.

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?

States a concrete verb and resource plus scope: saves a lot into the account's saved lots, with an optional note. An agent can tell this apart from mml_saved_lots (listing) and mml_find_lot (search). It does not, however, distinguish 'save' from the watch/unwatch family, which is the one remaining ambiguity.

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?

The line 'Spends no lookup' implicitly tells an agent this is the cheaper path compared to lookup-consuming siblings, which is useful usage context. But there is no explicit when-to-use/when-not statement and no sibling is named as an alternative, so the guidance remains 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