Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Stocks in a watchlist

watchlist_get
Read-onlyIdempotent

Retrieve the stocks in a specific Stockbit watchlist with price, change, and volume data. Use page and limit controls to browse results when the list is long.

Instructions

The stocks of one watchlist with price, change and volume.

Returns (Stockbit's data field): data{result[{company_id, symbol, name, ...price fields}], total, ...} - next page while result.length==limit

Endpoint: GET exodus /watchlist/{watchlistId}.

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": {
      "watchlistId": "<watchlistId>"
    },
    "name": "watchlist_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based Default 1.
limitNolimit Default 100.
watchlistIdYeswatchlist_id from GET /watchlist

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description goes beyond them by disclosing the response envelope (data.result, total, extra fields), the pagination continuation condition, and the underlying endpoint, which an agent cannot learn from the annotations or schema alone. It omits auth requirements and error behavior, keeping it short of a 5.

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?

It is short and front-loaded: purpose first, then return shape, then endpoint. There is minor noise from ellipses ('...price fields', 'total, ...') and vendor-specific phrasing ('Stockbit's data field'), but no sentence is padding.

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 carries the burden of explaining returns and does so reasonably: result array contents, a total, and the pagination termination signal. For a simple read-only list tool this is close to sufficient; only auth/error semantics and a precise statement of what 'total' counts are missing.

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 the baseline would be 3 on parameter documentation alone. The description adds genuine meaning by tying 'limit' to the pagination decision rule ('next page while result.length==limit') and by describing the shape of the first page, which the schema's one-line parameter descriptions do not convey.

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 states a specific resource ('the stocks of one watchlist') and enumerates the fields returned (price, change, volume), which lets an agent distinguish this from watchlist_list (which would return watchlists themselves). It stops short of naming any sibling explicitly, so differentiation is inferential 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 or when-not-to-use guidance and no mention of alternatives such as watchlist_list or watchlist_favorites. The only routing hint is schema-side ('watchlist_id from GET /watchlist'), and the pagination rule ('next page while result.length==limit') is procedural rather than a usage rule.

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