Skip to main content
Glama

Stop a watch

mml_unwatch
Idempotent

Stops a watch by its watch id. MapMyLot sends no more emails about that lot or suburb.

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": {
      "watch_id": "<watch_id>"
    },
    "name": "mml_unwatch"
  }
}

Input Schema

NameRequiredDescriptionDefault
watch_idYesThe watch id, as listed in the account's watches

Output Schema

NameRequiredDescriptionDefault
idYes
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?

The annotations already declare this is a non-read-only, idempotent, non-destructive operation. The description adds meaningful behavioral context by explaining the user-visible effect: no further emails about that lot or suburb.

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 with no wasted wording. The action and its effect are front-loaded, making the definition easy to scan.

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?

For a one-parameter tool with full schema coverage, annotations, and an output schema, the description covers the action and its consequence adequately. A minor gap is that it does not explain how to obtain the watch id, though the schema addresses that.

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%, and the single watch_id parameter is fully documented in the schema as listed in the account's watches. The description confirms that the watch id identifies the watch but adds no syntax or lookup details beyond the schema.

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?

The description states a specific verb and resource: it stops a watch identified by its watch id. That is clear enough to distinguish it from mml_watch and mml_watches, though it does not explicitly name the counterpart tool.

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 by the phrase 'Stops a watch by its watch id,' but the description gives no explicit when-to-use or when-not-to-use guidance. It also does not point to mml_watches for discovering watch ids.

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