Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Rename a watchlist

watchlist_rename

Renames an existing Stockbit watchlist by ID and updates its description, so you can keep watchlist names and notes accurate.

Instructions

Renames a watchlist (and sets its description).

Endpoint: PUT exodus /watchlist/{id}.

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": {
      "watchlist_id": "<watchlist_id>",
      "name": "<name>"
    },
    "name": "watchlist_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNew name.
descriptionNoDescription; default the name.
watchlist_idYesWatchlist id, from watchlist_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true. The description adds one genuinely useful behavioral fact not in the annotations: this call also writes the description field, not just the name. It does not say whether the existing description is overwritten, nor what happens on failure, so the addition is modest.

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?

Two short front-loaded sentences with the endpoint tacked on; nothing is padded. The endpoint notation is slightly cryptic ("exodus /watchlist/{id}") but does not obscure the purpose.

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

Completeness3/5

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

For a simple three-parameter mutation with full schema coverage and annotations, the essentials are present. However, the side effect of overwriting an existing description and the source of watchlist_id (only in the schema) are not reinforced, leaving a small gap for an agent invoking it blindly.

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 description coverage is 100%, so name, description and watchlist_id are already documented, including "Description; default the name." The phrase "sets its description" hints at overwrite semantics but does not spell out what happens to a pre-existing description when the field is omitted, so value beyond the schema is marginal.

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 uses a specific verb and resource ("Renames a watchlist") and adds a secondary effect ("sets its description"), which distinguishes it from sibling mutators like watchlist_add/remove/delete. There is no explicit differentiation sentence naming those siblings, so it stops short of a 5.

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 only implied: the agent must infer that this applies to an existing watchlist that is being renamed rather than created or deleted. No when-to-use / when-not-to-use guidance or prerequisites (e.g. ownership, id source) appear in the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools