Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Price summary of symbols

price_ladder
Read-onlyIdempotent

Retrieves valid tick price steps for a stock code to determine allowable order price increments around the current market price.

Instructions

Last price, change and basic quote fields for one or more symbols in one call.

Returns (Stockbit's data field): {message, data:{prices:int[]}} -- list of valid price steps (semantics inferred: tick ladder window around current price).

Endpoint: GET exodus /company-price-feed/prices.

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": {
      "stock_code": "<stock_code>"
    },
    "name": "price_ladder"
  }
}

Input Schema

NameRequiredDescriptionDefault
stock_codeYesstock_code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and with no output schema the return-format sentence genuinely earns its place by naming the payload shape {message, data:{prices:int[]}}. It also honestly flags that the semantics are inferred rather than documented. The cost is the inaccurate behavioral claim that it handles 'one or more symbols' and returns 'change and basic quote fields', which will set wrong expectations for callers.

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?

Three short lines, no filler, and the return shape and endpoint are compactly presented. The problem is ordering and accuracy rather than length: the front-loaded first sentence is the least reliable part of the definition, while the load-bearing clarification sits mid-paragraph in a parenthetical.

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 one-parameter read tool with no output schema, the definition does supply the payload shape and endpoint, which is the main missing piece elsewhere. It still leaves out what the integers mean operationally (currency, tick step unit, window bounds relative to current price) and gives no sibling routing, so an agent can call it but cannot confidently predict or place the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and there is a single required 'stock_code', so the schema baseline would be 3. However, the description actively conflicts with the schema by describing multi-symbol usage ('one or more symbols in one call') for a tool that accepts exactly one string, giving the agent a misleading model of cardinality rather than added meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The headline says 'Last price, change and basic quote fields for one or more symbols', but the stated return is {prices:int[]} — a list of valid price steps — and the title ('Price summary of symbols') reinforces the wrong framing. The tool name 'price_ladder' and the parenthetical 'tick ladder window around current price' are the only places the real function surfaces, so the definition argues with itself about what the tool does.

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 and no exclusions, despite many close siblings (price_latest, price_snapshot, price_by_board, price_orderbook, price_chart). An agent has no basis in this text for choosing price_ladder over price_latest for a quote or over price_snapshot for a summary.

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