Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Favorite watchlists

watchlist_favorites
Read-onlyIdempotent

Retrieve your favorite Stockbit watchlists in their saved order, with optional category filters and default visibility control.

Instructions

The watchlists marked favorite, in their order.

Returns (Stockbit's data field): data[{watchlist_id, name, category_type, is_favorite, ...}]

Endpoint: GET exodus /watchlist/favorite.

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_favorites"
  }
}

Input Schema

NameRequiredDescriptionDefault
category_typesNoRepeated key; UI [PORTFOLIO, NORMAL]
is_show_defaultNoUI true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 adds value beyond that by disclosing the ordering guarantee ('in their order') and the shape of the returned data field. It does not discuss pagination or whether the result can be empty.

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?

Three short lines with the purpose front-loaded, then return shape, then endpoint. The trailing '...' in the field list is slightly loose but the prose contains no wasted sentences.

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 sketches the returned data fields and notes the ordering, which is the key information an agent needs to consume the result. The two optional parameters rely on their schema descriptions, which is acceptable at 100% coverage.

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 both parameters (category_types, is_show_default) already carry documented meaning. The description adds nothing about how the filters interact with the 'favorite' scope, so the baseline 3 applies.

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 resource and scope: 'the watchlists marked favorite, in their order.' An agent can tell this returns a filtered subset of watchlists rather than the full list. It stops short of naming the sibling it contrasts with (watchlist_list), so it is clear but not sibling-differentiated.

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?

Usage is implied by the phrase 'marked favorite' — call this when you only want favorited watchlists. There is no explicit when-to-use/when-not guidance and no pointer to watchlist_list as the unfiltered alternative, leaving the routing inference to the agent.

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