Skip to main content
Glama
SiftingIO

siftingio-mcp

Official

Stock OHLCV bars

stocks_bars
Read-only

Fetch historical OHLCV bars for US equities over a date range at intervals from 1 minute to 1 hour. Specify ticker, start, end, interval, and paginate with cursor and limit.

Instructions

Fetch historical OHLCV bars for a US equity over a date/time range at a chosen interval (default 1m). Large ranges are size-capped (watch for the _truncated note) — narrow the window or paginate with cursor/limit. For a live price snapshot use last_trade or last_quote instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoInclusive upper bound. Default: now.
limitNoPage size (endpoint-specific default and max).
startNoInclusive lower bound: YYYY-MM-DD (NYSE local) or RFC3339 (UTC).
cursorNoOpaque cursor from a previous response's meta.next_cursor.
tickerYesUS equity ticker, e.g. AAPL.
intervalNoBar interval. Default 1m.
Behavior4/5

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. Description adds concrete behavioral details: size caps, _truncated note, and pagination mechanism, which are not in annotations.

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?

Three sentences, each with distinct purpose: purpose, limitation/solution, alternative. Front-loaded and no extraneous text.

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?

Covers key aspects (large-range handling, pagination, alternative tools) but does not describe the output format (OHLCV fields) which is essential since there is no output schema. Slightly incomplete but still informative.

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 each parameter already has a description. The tool description adds only minor context about default interval (1m) and pagination hints. No significant parameter clarification beyond schema.

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?

Clearly states 'Fetch historical OHLCV bars for a US equity over a date/time range at a chosen interval', specifying verb, resource, and scope. Distinguishes from live-price siblings (last_trade, last_quote) and implicitly from crypto_bars/forex_bars by restricting to US equities.

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?

Explicitly guides handling of large ranges via narrowing window or pagination, and directs to alternatives for live prices. However, does not explicitly exclude usage for non-historical scenarios like streaming.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SiftingIO/siftingio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server