Skip to main content
Glama

Get price bars

get_bars
Read-onlyIdempotent

OHLCV price bars for an instrument over a time range. Instrument ids are bare Hyperliquid symbols (BTC, HYPE) or dex-prefixed HIP-3 symbols (xyz:TSLA) — exactly the symbol values scan_markets returns. For a US stock, pass ref:eq:TICKER (for example ref:eq:NVDA): it reads the Databento US equity bars, which include pre-market and post-market minutes. Intervals are 1m/5m/15m/1h/1d; start/end default to the last 24h. Returns [timestamp, {o,h,l,c,v}] series with a meta envelope (caps applied server-side). (Requires api:read.)

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": {
      "instrument_id": "<instrument_id>",
      "interval": "<interval>"
    },
    "name": "get_bars"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoRFC 3339 end, e.g. 2026-07-02T00:00:00Z (default: start+24h, or now)
startNoRFC 3339 start, e.g. 2026-07-01T00:00:00Z (default: end-24h, or now-24h)
intervalYes
max_pointsNo
instrument_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered; the description adds real value beyond them by disclosing the auth requirement (api:read), server-side caps surfaced in a meta envelope, and the fact that equity data draws on a different upstream source. It does not explain what happens when a request exceeds caps (truncation vs downsampling) or any rate limits, which is the remaining behavioral gap.

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 return payload and the identifier rule, then interval/date defaults, then output shape. Sentences are dense but each carries distinct information (symbol routing, equity source, interval enum, defaults, caps). Slight over-packing of identifier forms into one paragraph makes it harder to scan than a short bulleted list would.

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?

With no output schema, the description usefully specifies the return shape ([timestamp, {o,h,l,c,v}] plus a meta envelope), so an agent knows what it will parse. Given 5 parameters at 40% coverage, only max_points is left unaddressed. A note on cap-exceeded behavior would close the final gap.

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?

Schema coverage is only 40%, and the description compensates substantially: it enumerates allowed intervals (1m/5m/15m/1h/1d), explains start/end defaulting, and spends the most text on instrument_id format variants that the schema leaves undocumented. max_points still has no explanation anywhere, though the 'caps applied server-side' note hints at server-enforced limits rather than client control.

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?

Opens with a specific verb+resource and scope: 'OHLCV price bars for an instrument over a time range.' It also anchors the instrument namespace to a sibling ('exactly the `symbol` values scan_markets returns'), which helps an agent place it in the tool graph. It stops short of distinguishing itself from nearby read tools like get_prices or get_live_snapshot, so an agent must infer when historical bars beat a latest-price call.

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?

Gives concrete selection guidance for the biggest ambiguity: which identifier form to pass for Hyperliquid spot, dex-prefixed HIP-3 symbols, and US equities via ref:eq:TICKER with the note that Databento bars include pre/post-market minutes. Defaults (start/end to the last 24h) are stated for the common case. It lacks explicit when-not-to-use guidance versus get_prices or get_live_snapshot, so there are no exclusions.

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.

Resources