Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Daily OHLCV bars

price_daily_bars
Read-onlyIdempotent

Retrieve daily open, high, low, close, volume, and value bars for one stock symbol between two dates to build charts and calculate indicators.

Instructions

Daily candles (open, high, low, close, volume, value) of one symbol between two dates, for charting and indicators.

Returns (Stockbit's data field): data{chartbit[{unixdate (sec, +25200 added client-side), open, high, low, close, lot, value, frequency}], previous_timestamp} newest first (client reverses). Volume series picks lot (default) / value / frequency.

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

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

Input Schema

NameRequiredDescriptionDefault
limitNoAlways 0 when from/to present. Default 0.
symbolYessymbol
end_dateNoNewest date, YYYY-MM-DD. Default today.
start_dateNoOldest date, YYYY-MM-DD. Default one year ago.

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 readOnly, idempotent, non-destructive and open-world, so safety is covered. Beyond that, the description discloses the return envelope (data.chartbit with field names), ordering (newest first, client reverses), the +25200 unixdate offset, and that the volume series is selectable via lot/value/frequency — meaningful behavior not present in the structured fields.

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?

Front-loaded with the payload definition, then returns, then endpoint — a sensible ordering with little waste. Some internal shorthand ('exodus', 'chartbit', the client-side +25200 note) is terse but relevant to consumers of the response.

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?

There is no output schema, so the description carries the burden of describing the response, and it does so with concrete field names and ordering. Missing only edge-case behavior on empty ranges or pagination, which is a minor gap for a date-bounded read tool.

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 coverage is 100%, so all four parameters including the odd 'limit must be 0 when from/to present' rule are already documented in the schema. The description adds the 'between two dates' framing but no syntax or format meaning beyond that, which is the baseline-worthy outcome.

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 verb+resource: daily OHLCV candles for one symbol between two dates, plus the endpoint. The word 'daily' implicitly distinguishes it from price_intraday_bars, but no sibling is named explicitly, so differentiation is left to inference.

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?

The description gives a use context ('for charting and indicators') but never states when to choose this over price_intraday_bars, price_history, or price_chart, and offers no exclusions or prerequisites.

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