Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Remove a stock from a watchlist

watchlist_remove
Destructive

Removes a single stock symbol from a specified Stockbit watchlist by watchlist ID and ticker, letting you keep a curated list current after a symbol no longer needs tracking.

Instructions

Removes one symbol from a watchlist.

Endpoint: DELETE exodus /watchlist/{id}/company/{companyId}/item.

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>",
      "symbol": "<symbol>"
    },
    "name": "watchlist_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesIDX ticker such as BBCA or TLKM (no exchange prefix).
watchlist_idYesWatchlist id, from watchlist_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is fully covered structurally. The description adds nothing beyond that — it does not say what happens if the symbol is not present, whether the operation is reversible, or any permission requirements. Only the raw HTTP endpoint is appended, which adds little behavioral insight.

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?

The first sentence is tight and front-loaded. The second sentence exposes an internal HTTP endpoint whose path uses 'companyId' while the actual parameter is 'symbol', introducing a naming mismatch that is more noise than signal for an agent.

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 two-parameter, fully documented mutation tool with no output schema, the description plus annotations give enough to call it correctly. The main omission is failure behavior when the symbol is absent, but given strong annotation coverage the definition is largely sufficient.

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%, with both parameters documented (ticker format and origin from watchlist_list), so the baseline of 3 applies. The description mentions 'one symbol' and 'watchlist', which merely restates the schema rather than adding format or constraint detail.

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: 'Removes one symbol from a watchlist.' The word 'one' clarifies it is a single-item removal rather than whole-list deletion, which implicitly separates it from watchlist_delete. It does not name any sibling explicitly, 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 Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of any alternative tool. An agent must infer from sibling names that watchlist_add is the inverse and watchlist_delete removes entire lists; the description itself provides no routing signal.

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