Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Intraday bars

price_intraday_bars
Read-onlyIdempotent

Retrieve intraday OHLC price bars for one symbol over a short date range, including timestamp, open, high, low, close, lot, value, and frequency.

Instructions

Intraday candles of one symbol between two dates.

Use short ranges (a few days): intraday history is long.

Returns (Stockbit's data field): data{chartbit[{unix_timestamp, open, high, low, close, lot, value, frequency}], previous_timestamp}.

Endpoint: GET exodus /chartbit/{symbol}/price/intraday.

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": {
      "symbol": "<symbol>"
    },
    "name": "price_intraday_bars"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNolimit Default 0.
symbolYessymbol
end_dateNoNewest date, YYYY-MM-DD. Default today.
start_dateNoOldest date, YYYY-MM-DD. Default yesterday.
minutes_multiplierNoSent only for resolution '60'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered elsewhere. The description adds value beyond them by disclosing the return shape (chartbit array of timestamp/OHLC/lot/value/frequency plus previous_timestamp) and the underlying endpoint, which helps an agent understand output without an output schema. It says nothing about rate limits, pagination via limit, or error behavior.

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 sectioned -- purpose, range advice, return shape, endpoint -- with the core purpose front-loaded. The endpoint line and 'Stockbit's data field' phrasing add minor noise but little wasted text.

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?

With no output schema, the description usefully sketches the returned fields and the previous_timestamp cursor, which is the most important gap it fills. However, for a 5-parameter tool it leaves limit and minutes_multiplier behavior unexplained, so it is adequate rather than complete.

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 the schema already documents symbol, start_date, end_date, limit, and minutes_multiplier, making 3 the baseline. The description only restates the date-range concept and adds no meaning for limit (whose 'Default 0' is opaque) or minutes_multiplier.

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 gives a specific verb and resource -- 'Intraday candles of one symbol between two dates' -- which clearly separates it from a daily-bars or latest-price tool. It is clear and specific, though it never names the sibling (price_daily_bars) that an agent might confuse it with.

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?

It gives one real usage constraint: 'Use short ranges (a few days): intraday history is long,' which steers range sizing. It does not state when to prefer this over price_daily_bars or price_chart, nor any prerequisites, so guidance is implied rather than explicit.

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