Skip to main content
Glama

FinanceQuery

Price Chart (OHLCV)

get_chart
Read-onlyIdempotent

Get historical OHLCV candlestick chart data for one or more stock symbols (comma-separated). A single symbol supports start/end absolute timestamps and returns one chart; multiple symbols return a batch of charts plus per-symbol errors (interval/range only, no start/end).

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": {
      "symbols": "<symbols>",
      "interval": "<interval>",
      "range": "<range>"
    },
    "name": "get_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd date as Unix timestamp (seconds). Defaults to now when `start` is set.
limitNoMaximum candles per page; omitted = curated default (25)
rangeYesTime range: 1d|5d|1mo|3mo|6mo|1y|2y|5y|10y|ytd|max (default: 1mo). Ignored when `start` is set.
startNoStart date as Unix timestamp (seconds). When provided, overrides `range`.
cursorNoOpaque continuation token from a previous response's `pageInfo.endCursor`; omitted = first page
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default set
symbolsYesOne or more comma-separated ticker symbols (e.g., "AAPL" or "AAPL,MSFT,GOOG")
intervalYesCandle interval: 1m|5m|15m|30m|1h|1d|1wk|1mo|3mo (default: 1d)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. Beyond that, the description adds genuinely new behavior: multi-symbol calls return a batch of charts plus per-symbol errors, and start/end are unsupported in that mode. It does not mention pagination via cursor or the default page size, but the added error/batching semantics are substantive.

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?

Two tight sentences, front-loaded with the resource and scope, then the mode distinction. No filler and nothing repeated from the title or annotations.

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 an 8-parameter tool with no output schema, the description covers what the tool returns, the single-vs-multi mode split, and per-symbol error handling. Pagination (cursor/limit) and field selection return shape are left to the schema, which is acceptable but leaves a small gap for a batch tool.

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?

With 100% schema coverage the baseline is 3, and the description earns above that by disclosing a constraint the schema does not state: start/end are only valid for a single-symbol request, and interval/range are the only knobs in multi-symbol mode. That clarifies the interaction between the eight parameters in a way the schema text alone does not.

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 and resource ('Get historical OHLCV candlestick chart data') plus the scope ('one or more stock symbols, comma-separated'), so an agent knows exactly what it returns. It does not name or contrast any sibling tool, but the resource is distinct enough from the price-target/analysis siblings that confusion is unlikely.

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 mode-level guidance (single symbol supports start/end absolute timestamps; multiple symbols support interval/range only). That tells the agent how to pick between the two calling modes, but there is no guidance on when to choose this tool over alternatives such as indicators or price-target tools, so usage is only implied at the task level.

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.