Skip to main content
Glama

Set watchlist

set_watchlist

Watch or unwatch a coin. Widget-only: called from the marketplace widget.

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": {
      "coinId": "<coinId>",
      "watch": "<watch>"
    },
    "name": "set_watchlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
watchYes
coinIdYes
accessTokenNo
widgetTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the watch toggle but does not mention idempotency, authentication requirements despite accessToken and widgetToken parameters, failure modes, or whether repeated calls overwrite state. This is a significant gap for a mutation tool with zero annotation coverage.

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?

The description is two short sentences and front-loads the core action before the widget constraint. The second sentence is slightly repetitive ('Widget-only' and 'called from the marketplace widget'), but overall it is efficient and easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter mutation tool with no annotations, no output schema, and 0% schema description coverage, the description is too thin. It omits authentication context for the token parameters and does not describe the result of watch/unwatch, leaving an agent without enough to invoke it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, but it only indirectly explains coinId and watch through the phrase 'Watch or unwatch a coin.' The accessToken and widgetToken parameters receive no mention at all, leaving half the parameters undocumented in both schema and description.

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 pair (watch/unwatch) and resource (a coin), which is clear enough for an agent to know what the tool does. It does not explicitly distinguish itself from siblings like show_marketplace, but the widget-only scope provides some separation.

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?

The phrase 'Widget-only: called from the marketplace widget' gives a context for when the tool is available, but it does not say when an agent should choose this over alternatives or what to do outside the widget. Usage guidance is implied rather than explicit.

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