Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Watchlists

watchlist_list
Read-onlyIdempotent

Retrieve an account's Stockbit watchlists with IDs, names, categories, sizes, and optional company-follow status to inspect saved stock groups and track whether a company is included.

Instructions

The account's watchlists with their ids and sizes.

Returns (Stockbit's data field): data[{watchlist_id, name, description?, category_type, is_favorite, is_default, followed (with company_id), total_items (with with_total)}]

Endpoint: GET exodus /watchlist.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "watchlist_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_idNoWhen set, each group reports whether it contains this company ('followed')
with_totalNoInclude total_items per group
category_typesNoRepeated key; UI typically [ALL_WATCHLIST, NORMAL] or [ALL_WATCHLIST, PORTFOLIO, NORMAL]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds real value the annotations cannot: it reveals the response envelope (Stockbit's data field) and the per-item fields including the optional 'followed' and 'total_items' that only appear under certain inputs. It does not discuss pagination or limits, but that omission is minor for a small account-scoped list.

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?

Front-loaded with the resource and payload size, then a compact return-shape line and an endpoint line — three short, purposeful sentences. The endpoint line is of marginal use to an agent but is not wasteful enough to penalize further.

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?

With no output schema, the description usefully compensates by sketching the returned object, and all parameters are schema-documented. What is missing relative to the sibling set is routing guidance (list vs. get vs. favorites), which the description leaves to the reader.

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 all three optional parameters are already documented in the schema, which sets the baseline at 3. The description's return-shape line mirrors the effect of company_id and with_total but adds no syntax, default-value, or enum detail beyond the schema (e.g. the category_types token vocabulary is only in the schema).

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 account's watchlists with their ids and sizes" states a specific resource and the attributes it surfaces, which is enough to tell it apart from watchlist_get (single list) or watchlist_favorites. It stops short of naming those siblings explicitly, so the differentiation is implied rather than stated.

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 at all: nothing says to call this first to discover watchlist ids before watchlist_get, watchlist_add, or watchlist_remove, nor when watchlist_favorites would be preferable. The only usage hint is the word 'with_total'/'company_id' in the return line, which is indirect.

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