Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Delete a watchlist

watchlist_delete
Destructive

Deletes an entire Stockbit watchlist after confirmation via popup or preview token, preventing accidental removal. Provide the watchlist ID and name for the confirmation prompt.

Instructions

Deletes a whole watchlist. The user confirms first (a popup, or a preview and token).

Endpoint: DELETE 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": "watchlist_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
watchlist_idYesWatchlist id, from watchlist_list.
watchlist_nameNoIts name, shown in the confirmation.
confirmation_tokenNoOnly for clients without confirmation popups: the token a previous call returned with its preview. Send it only after the user has confirmed that preview.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true; the description adds the confirmation gate and the two confirmation modes, which is behavior an agent must know before invoking. It stops short of saying what happens to dependent alerts or what an error for a missing id looks like.

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: destructive scope first, confirmation requirement second, endpoint last. No filler or repetition.

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 destructive three-parameter tool with full annotation and schema coverage, the description supplies the operationally critical piece (the confirmation flow) and the endpoint. Only edge-case behavior for invalid or already-deleted ids is unaddressed, which is a minor gap.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning by explaining the confirmation_token branch: a preview call precedes it and the token is only for clients without popups. That clarifies how the parameters interlock beyond the per-field schema text.

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 ('Deletes a whole watchlist'), and 'whole' implicitly distinguishes it from the sibling watchlist_remove that removes individual entries. It never names that sibling, so the differentiation is left for the agent to infer.

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?

Explains the confirmation prerequisite (popup, or preview plus token) which is genuinely useful procedural context. However, it gives no explicit guidance on when to pick this over watchlist_remove or watchlist_create, and no exclusions, so usage is only implied by the word 'whole'.

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