Skip to main content
Glama

Watch a lot or its suburb

mml_watch
Idempotent

Watches a lot, or the suburb it is in. MapMyLot emails the account holder when the public data about it changes, at most once a day. Watching the same lot or suburb again changes nothing. Requires a MapMyLot Pro plan.

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

Input Schema

NameRequiredDescriptionDefault
scopeNolot: this lot; suburb: the suburb this lot is inlot
row_idYesThe lot's row_id, as returned by the lot search or in the list of purchased reports

Output Schema

NameRequiredDescriptionDefault
idYes
nameNoThe lot's address or the suburb's name
scopeYes
activeYes
pausedNoPaused while the account is not on Pro
row_idNo
parcel_idNo
checked_atNo
created_atNo
jurisdictionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (which already declare idempotentHint=true and destructiveHint=false), the description discloses the actual side effect — an email to the account holder — plus the daily frequency cap and the subscription prerequisite. That is genuine behavioral value the structured fields cannot convey. What remains unsaid is the failure mode when the account lacks Pro.

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?

Three front-loaded sentences, each carrying a distinct fact (what it does, what happens afterward, and the prerequisite). Nothing is repeated from the schema or annotations.

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 only two parameters, full schema coverage, and an output schema that handles return values, the description covers what an agent needs to invoke it correctly. The only shortfall is not stating the observable outcome when the Pro requirement is unmet.

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 enum documents lot vs suburb explicitly, so the description needs only to stay consistent — which it does. It adds no syntax or sourcing detail for row_id beyond what the schema already says. 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 specific verb ('Watches') and resource ('a lot, or the suburb it is in'), and the scope distinction is carried both in the prose and in the enum. It does not explicitly name mml_unwatch or mml_watches as the inverse/listing counterparts, so sibling differentiation is inferred rather than stated.

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?

Gives clear operating context: notifications fire on public-data changes, capped at once per day, and the call is a no-op if the watch already exists. The Pro-plan prerequisite is a real gating condition, but it never points to mml_unwatch for stopping a watch or mml_watches for inspecting existing ones.

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