Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Market mover categories

market_mover_options
Read-onlyIdempotent

Retrieve available mover types, default selection, and stock filter options for a Stockbit market mover category so you can configure mover queries correctly.

Instructions

The mover types available in one category, e.g. MOVER_CATEGORY_IEPIEV_MOVER (pre-opening).

Returns (Stockbit's data field): data{available_mover_types[6 IEP/IEV/IEVAL types], default_mover_type 'MOVER_TYPE_IEVAL_TOP_GAINER', available_filter_stocks[...incl. SPECIAL_MONITORING_BOARD]}.

Endpoint: GET exodus /order-trade/market-mover/{category}/options.

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": {
      "category": "<category>"
    },
    "name": "market_mover_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYescategory
filter_stocksNoRepeated key. Default ["FILTER_STOCKS_TYPE_MAIN_BOARD","FILTER_STOCKS_TYPE_DEVELOPMENT_BOARD","FILTER_STOCKS_TYPE_ACCELERATION_BOARD","FILTER_STOCKS_TYPE_NEW_ECONOMY_BOARD"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile needs no restating. The description adds genuine value by disclosing the return shape (available_mover_types, default_mover_type, available_filter_stocks) in the absence of an output schema, but it says nothing about auth requirements, rate limits, or what happens with an invalid category.

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?

It is short and starts with the core purpose, but the return-value sentence is a dense run-on of raw field names with bracketed enumerations that reads more like pasted API output than guidance. The trailing endpoint line is compact and useful; the middle sentence could be tightened.

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 read with no output schema, the definition covers the essential ground: what it returns, the field names, a valid category example, and a filter default. The absence of any statement about how the returned mover types and default should be used downstream is the remaining gap.

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 is 3; the description exceeds it by supplying a concrete category example (MOVER_CATEGORY_IEPIEV_MOVER) where the schema only says 'category', and by echoing that filter_stocks can include SPECIAL_MONITORING_BOARD. It does not explain the interaction between category and filter_stocks.

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 names a specific resource — the mover types available within one market-mover category — and anchors it with a concrete example value (MOVER_CATEGORY_IEPIEV_MOVER for pre-opening) plus the underlying endpoint. An agent can tell this is a configuration/options lookup rather than a data query, but nothing distinguishes it from the sibling market_movers tool that presumably consumes these values.

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 explicit when-to-use guidance, no mention of when not to call it, and no reference to market_movers or any sibling as the consumer of its output. The discovery role (fetch valid categories before calling a movers endpoint) is only inferable from the word 'options' in the endpoint path.

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