Skip to main content
Glama

List watched products

list_watched
Read-onlyIdempotent

The products on the signed-in account's Deal.ai wish list, whose price drops it is e-mailed about: each one's best store price now and where, with when it was seen, its reference price (the price when it was saved or last e-mailed), and its deal.ai page; and whether the account's price alerts are on.

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": "list_watched"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety burden is covered elsewhere. The description does add real context beyond that: results are scoped to the signed-in account, include current best store price, and report whether price alerts are enabled. It says nothing about pagination, empty-list behavior, or auth failure modes.

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

Conciseness3/5

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

It is a single dense sentence that crams return fields into nested parentheticals and a semicolon clause, making it harder to scan. Nothing is truly wasted, but it is not front-loaded with the action and could be split into a purpose clause plus a returns clause.

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?

There is no output schema, so the description usefully enumerates the returned fields: best store price and store, sighting time, reference price with its definition, deal.ai page link, and alert status. That is close to complete for a zero-parameter read tool; only list size/pagination and empty-result behavior are unaddressed.

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, so per the baseline this scores 4. There is no parameter syntax or filtering behavior an agent needs to supply, and the description correctly implies the implicit account-scoped filter instead of a parameter.

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 names the specific resource and scope: the signed-in account's Deal.ai wish list of price-drop-watched products. That distinguishes it from generic search/price siblings without needing to know their schemas. It loses a point because it is a noun phrase with no verb ('List'/'Returns'), so the operation type must be inferred from the tool name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no alternative is named. The wish-list framing implies 'call this to see what you're watching', but an agent gets no routing help versus watch_price, stop_watching, get_product_prices, or check_deal.

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.