SNACS Data

Intraday Bars

snacs_intraday_bars_get

Read-only

Intraday OHLCV bars for a ticker, newest first: 1m, 5m, 15m, 1h or 4h bars, covering at most 7, 31, 92, 366 or 1,096 days per call. Each bar's time is its start (UTC). When the page is full, pass next_before back as before to read older bars.

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": "snacs_intraday_bars_get"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max bars, newest first (up to 500).
`before`	No	Only bars starting before this instant (ISO 8601 with an offset); pass a page's next_before to read the older page.
`ticker`	Yes	U.S. ticker symbol, e.g. GPUS.
`date_to`	No	Last Eastern trading day, YYYY-MM-DD (inclusive); default today.
`interval`	No	Bar size: '1m', '5m', '15m', '1h' or '4h'.	5m
`date_from`	No	First Eastern trading day, YYYY-MM-DD (inclusive).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description's value is in operational detail, and it delivers: result ordering is newest-first, each bar's timestamp is its start time in UTC, and the pagination contract is spelled out. It does not mention rate limits, but that is a minor omission given the otherwise solid disclosure.

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?

Three sentences, front-loaded with the resource and ordering, then constraints, then pagination. No filler. The only friction is the parallel ordering of the interval and day-limit lists, which costs a moment of parsing.

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?

An output schema exists, so return shape and next_before needn't be re-explained, and the description correctly just tells the agent how to feed next_before back in. For a six-parameter read tool the description covers ordering, timezone of bar timestamps, and window limits. It stops short of routing between this and the daily-bars sibling.

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 100%, so the baseline is 3; the description exceeds it by adding the interval-to-lookback-window mapping, which the schema never states, and by clarifying the before/next_before cursor relationship. The parallel list ('7, 31, 92, 366 or 1,096 days') requires the reader to align positions with the interval list to know which limit belongs to which interval, which is a small ambiguity.

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?

Names a specific resource and scope: 'Intraday OHLCV bars for a ticker, newest first', and enumerates the supported intervals and per-call lookback limits. It does not explicitly contrast itself with the sibling snacs_bars_get (presumably daily bars), so the agent must infer that split from the names alone.

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?

Gives clear operative guidance within the tool: pick one of five intervals, and the lookback window shrinks as granularity increases (7/31/92/366/1096 days). Pagination guidance is explicit ('pass next_before back as before to read older bars'). However, there is no statement of when to prefer this over the sibling bars tool, nor any prerequisite or exclusion.

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

All SNACS Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.