Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Add a stock to a watchlist

watchlist_add

Adds one stock symbol to a specified watchlist, resolving the company ID needed by Stockbit so the ticker can be tracked in that list.

Instructions

Adds one symbol to a watchlist (the tool looks up the company id Stockbit needs).

Endpoint: POST exodus /watchlist/{id}/company/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_add"
  }
}

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

B3.2/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, so the safety profile is covered. The description does add genuine context beyond that: the internal company-id lookup, which explains why an invalid or ambiguous ticker may fail. It does not address what happens when the symbol is already present (notable given idempotentHint=false) or what a successful response 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and the useful lookup detail, followed by an endpoint line that helps agents map behavior to the API. The endpoint string is somewhat low-value for an agent but is a single short line, not bloat.

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 two-parameter mutation with no output schema and full annotation coverage, the definition is workable but stops short: it never says what is returned, how duplicates are handled given idempotentHint=false, or what errors occur when the symbol can't be resolved to a company id — the very lookup it calls 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 description coverage is 100% and already documents the IDX ticker format (

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: 'Adds one symbol to a watchlist', plus the non-obvious side effect that the tool internally resolves the company id Stockbit requires. It is clearly distinct from the sibling mutators (watchlist_remove deletes, watchlist_create makes a list), though it never names those siblings to reinforce the boundary.

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?

No sentence says when to use this versus watchlist_remove, watchlist_create, or watchlist_favorites, and no preconditions are stated. The only usage hint ('watchlist id, from watchlist_list') lives in the schema, not the description, so the prose itself offers no routing guidance.

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