Skip to main content
Glama

Change the products you watch (Record plan)

set_watched_products
DestructiveIdempotent

Replaces the list of products the signed-in Record account watches, which decides its alerts and its Home list. Send every product to keep, by name. An empty list means every product, including ones Provkeep adds later.

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": {
      "products": "<products>"
    },
    "name": "set_watched_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
productsYesProduct names, e.g. BPC-157. Empty watches everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the risk profile is known. The description adds useful context beyond that — that the previous watch list is discarded, that alerts and the Home list are affected, and that an empty list also opts into future Provkeep-added products. It does not say what happens when a supplied name is unknown, which is the main behavioral unknown for a destructive batch write.

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 short sentences, front-loaded with purpose, then the calling rule, then the edge case. Nothing is redundant and nothing is buried.

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 no output schema and annotations covering safety, this covers purpose, replacement semantics, side effects, and the empty-list behavior. The remaining gap is error behavior for invalid product names, which the description neither promises nor rules out.

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 parameter already documents names and the empty-list case, so the baseline applies. The description does add one thing the schema does not: that the array must contain every product to keep rather than a delta — a meaningful semantic clarification.

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?

Uses a specific verb and resource: 'Replaces the list of products the signed-in Record account watches,' and even names the downstream effects (alerts, Home list). It is clearly distinct from the read tool list_watched_products by virtue of the full-replacement semantics, though it never names that sibling explicitly.

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 real operational guidance: 'Send every product to keep' makes clear this is a complete-set operation, not an incremental add, and it defines the important empty-list edge case. It stops short of advising the agent to first read the current watchlist via list_watched_products, which matters for a destructive overwrite.

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