Skip to main content
Glama

DealMonitor

watch_price

Set a price alert: keep watching a product's price and notify the account owner when it reaches the target. Use this for any 'tell me when this drops', 'notify me at X', 'monitor this price' or 'keep an eye on this' task. Reads the current price in the same call, so one call answers both 'what does it cost now' and 'tell me when it gets cheaper'. The watch keeps running after this conversation ends. Requires an API token.

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": {
      "url": "<url>",
      "target_price": "<target_price>"
    },
    "name": "watch_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
target_priceYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full load, and it does meaningful work: it discloses the persistent side effect ('The watch keeps running after this conversation ends'), the notification behavior (alerts the account owner), and an auth prerequisite ('Requires an API token'). It does not mention whether duplicate watches can be created or how to cancel one, but the core behavior is well surfaced.

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?

Front-loaded with the core action, then usage triggers, then the key behavioral note and prerequisite. Every sentence carries information; the quoted example phrases cost some length but earn it by mapping natural user intent to the tool.

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 values need no explanation, and the description covers persistence, notification target, and auth. The remaining hole is the ambiguity around url and target_price units, which matters for a two-required-parameter tool with no schema descriptions.

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 0%, so the description must compensate for both parameters. It implies url points at a product ('a product's price') and that target_price is the threshold the price must 'reach', but it never specifies URL format, accepted retailers, or currency/unit semantics for the target. That is partial compensation only.

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: 'Set a price alert: keep watching a product's price and notify the account owner when it reaches the target.' It also clarifies that the call returns the current price, which separates it from a pure read. It stops short of distinguishing itself from a sibling like set_target_price, so an agent must infer that difference from context.

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?

Explicit trigger phrases ('tell me when this drops', 'notify me at X', 'monitor this price', 'keep an eye on this') give a clear picture of when to reach for this tool. It does not say when NOT to use it or name an alternative (check_price, set_target_price, stop_watching), which is the main gap.

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