Skip to main content
Glama

My saved lots

mml_saved_lots
Read-onlyIdempotent

Lists the lots this account has saved on MapMyLot (the site's shortlist), newest first, with the stored fields and a link to each. Returns no lot facts. 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_saved_lots"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
lotsYes
countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description still adds real value with ordering ('newest first'), the fact that stored fields plus a link are returned, and the cost hint 'Spends no lookup'. It stops short of saying what happens when the shortlist is empty or whether results are paginated.

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?

Two short sentences, front-loaded with the resource and scope, then the ordering and cost qualifiers. Nothing is redundant and every clause carries information.

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 shape need not be explained, and the description correctly covers ordering, content type and cost for a zero-parameter read. The only meaningful gap is the saved-versus-watched distinction, which matters given the mml_watches siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is an empty object at 100% coverage, so there is nothing the description could meaningfully add beyond what is already structured. Baseline 4 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?

States a specific verb and resource — 'Lists the lots this account has saved on MapMyLot (the site's shortlist), newest first' — and adds that it returns no lot facts, implicitly contrasting with the fact-fetching siblings. It does not, however, distinguish saved lots from watched lots (mml_watches/mml_watch), which is the closest adjacent concept.

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: 'Returns no lot facts' and 'Spends no lookup' hint that this is the cheap route for listing saved items, but the description never says when to pick this over mml_lot_facts, mml_watches, or mml_compare_lots, nor any exclusions.

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