Skip to main content
Glama

get_ohlcv

Read-only

End-of-day OHLCV candles for one ticker, daily or weekly (weeks dated by Sunday). Paged: pass next_cursor back as cursor, or use store_as with fetch_all for the whole range in one call.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_ohlcv"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd, inclusive (YYYY-MM-DD).
limitNoDefault 100.
orderNoDefault desc.
startNoStart, inclusive (YYYY-MM-DD).
appendNoAdd rows to an existing store_as table instead of replacing it.
cursorNonext_cursor from the previous page.
tickerYese.g. AAPL
store_asNoTable name: store rows in SQLite, return only a summary. Read with query_data.
fetch_allNoFollow every page into store_as in this one call.
timeframeNoDefault daily.
adjustmentNosplit (default), split_dividend (total return) or raw (as traded).

Output Schema

NameRequiredDescriptionDefault
dataNoThe tool's result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / adjustment / description
      Previous value: -"Default split; split_dividend = total return."New value: +"split (default), split_dividend (total return) or raw (as traded)."
    • changedInput schema / properties / timeframe / description
      Previous value: -"Default: daily (every plan reads daily and weekly)."New value: +"Default daily."
  2. Changed12 schema fields changed
    • changedInput schema / properties / adjustment / description
      Previous value: -"Price basis. split (default): today's share basis, every split applied. split_dividend: splits plus cash dividends (a total-return series). raw: as traded on each date (daily only for ohlcv)."New value: +"Default split; split_dividend = total return."
    • addedInput schema / properties / append
      Added value: +{
      +  "description": "Add rows to an existing store_as table instead of replacing it.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / cursor / description
      Previous value: -"Exclusive date cursor from next_cursor for pagination (YYYY-MM-DD)."New value: +"next_cursor from the previous page."
    • changedInput schema / properties / end / description
      Previous value: -"Inclusive end date (YYYY-MM-DD). Compared against the candle date."New value: +"End, inclusive (YYYY-MM-DD)."
    • addedInput schema / properties / fetch_all
      Added value: +{
      +  "description": "Follow every page into store_as in this one call.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum candles to return (1-1000). Default: 100."New value: +"Default 100."
    • changedInput schema / properties / order / description
      Previous value: -"Sort by candle date. Default: desc."New value: +"Default desc."
    • changedInput schema / properties / start / description
      Previous value: -"Inclusive start date (YYYY-MM-DD). Compared against the candle date, so for weekly this is the Sunday week end. Lookback is limited by plan."New value: +"Start, inclusive (YYYY-MM-DD)."
    • addedInput schema / properties / store_as
      Added value: +{
      +  "description": "Table name: store rows in SQLite, return only a summary. Read with query_data.",
      +  "type": "string"
      +}
    • changedInput schema / properties / ticker / description
      Previous value: -"Ticker symbol, e.g. AAPL, BTCUSD, SPY"New value: +"e.g. AAPL"
    • changedInput schema / properties / timeframe / description
      Previous value: -"Candle timeframe. Daily snapshots are Pro and Commercial only (Free and Plus read weekly; daily returns 403). Default: daily on Pro and Commercial, weekly on Free and Plus. Weekly candles cover Monday-Sunday and are dated by the Sunday week end, matching get_summary with timeframe=weekly. The in-progress week is not returned."New value: +"Default: daily (every plan reads daily and weekly)."
    • changedOutput schema / properties / data / description
      Previous value: -"The TickerDB API response payload for this tool call."New value: +"The tool's result."
  3. Changed1 schema field changed
    • changedInput schema / properties / timeframe / description
      Previous value: -"Candle timeframe. Default: daily. Weekly candles cover Monday-Sunday and are dated by the Sunday week end, matching get_summary with timeframe=weekly. The in-progress week is not returned."New value: +"Candle timeframe. Daily snapshots are Pro and Commercial only (Free and Plus read weekly; daily returns 403). Default: daily on Pro and Commercial, weekly on Free and Plus. Weekly candles cover Monday-Sunday and are dated by the Sunday week end, matching get_summary with timeframe=weekly. The in-progress week is not returned."
  4. Changed1 schema field changed
    • addedInput schema / properties / adjustment
      Added value: +{
      +  "description": "Price basis. split (default): today's share basis, every split applied. split_dividend: splits plus cash dividends (a total-return series). raw: as traded on each date (daily only for ohlcv).",
      +  "enum": [
      +    "split",
      +    "split_dividend",
      +    "raw"
      +  ],
      +  "type": "string"
      +}
  5. Changed3 schema fields changed
    • changedInput schema / properties / end / description
      Previous value: -"Inclusive end date (YYYY-MM-DD)."New value: +"Inclusive end date (YYYY-MM-DD). Compared against the candle date."
    • changedInput schema / properties / start / description
      Previous value: -"Inclusive start date (YYYY-MM-DD). Lookback is limited by plan."New value: +"Inclusive start date (YYYY-MM-DD). Compared against the candle date, so for weekly this is the Sunday week end. Lookback is limited by plan."
    • addedInput schema / properties / timeframe
      Added value: +{
      +  "description": "Candle timeframe. Default: daily. Weekly candles cover Monday-Sunday and are dated by the Sunday week end, matching get_summary with timeframe=weekly. The in-progress week is not returned.",
      +  "enum": [
      +    "daily",
      +    "weekly"
      +  ],
      +  "type": "string"
      +}
  6. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already state readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the description's job is to add context. It does add useful traits: weeks are dated by Sunday, the response is paged, and store_as returns only a summary while writing rows to a SQLite table read with query_data. It does not flag that store_as replaces an existing table unless append is set, which is a mildly destructive local side effect left implicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is two dense sentences with zero filler. The core purpose comes first, then the paging and bulk-fetch mechanics, so an agent can act after the first clause.

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?

Given an 11-parameter tool with an output schema, this is nearly complete. It covers scope, paging, and the storage mode; only the interaction between replace and append, and when to choose daily or weekly, are left to the schema.

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 every parameter is already documented, which sets a baseline of 3. The description adds meaning beyond the schema only for the cursor/next_cursor round-trip and the store_as+fetch_all pairing; the remaining parameters add nothing beyond what the schema states.

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

Purpose5/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: end-of-day OHLCV candles for a single ticker, with the daily/weekly scope stated up front. An agent can tell immediately what it returns, unlike the neighbouring get_market or get_summary tools, which pull other data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear paging guidance: pass next_cursor back as cursor, or use store_as with fetch_all to get the whole range in one call. It does not name when to prefer this over a sibling tool such as get_market, and it does not say when to use daily vs weekly, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.