Skip to main content
Glama
signal8ai

Signal8 MCP Server

Official
by signal8ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Intraday Price Bars

get_intraday_bars
Read-only

Fetch intraday OHLCV bars at 1, 5, 15, 30, or 60-minute resolution for stock tickers. Includes extended-hours data for 1-minute bars, enabling premarket and after-hours analysis.

Instructions

Get intraday OHLCV candles at 1, 5, 15, 30, or 60-minute resolution. Use for intraday price action analysis, volume patterns, and short-term technical analysis. Returns open, high, low, close, and volume for each bar. Set extended=true (1-minute resolution only) to include premarket (04:00–09:30 ET) and after-hours (16:00–20:00 ET) bars.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesEnd time as UNIX timestamp
fromYesStart time as UNIX timestamp
tickerYesStock ticker symbol (e.g., "AAPL", "TSLA")
extendedNoInclude extended-hours bars (premarket 04:00–09:30 ET and after-hours 16:00–20:00 ET). Only supported with resolution "1".
resolutionYesBar resolution in minutes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / extended
      Added value: +{
+  "description": "Include extended-hours bars (premarket 04:00–09:30 ET and after-hours 16:00–20:00 ET). Only supported with resolution \"1\".",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true. The description adds behavioral details: extended-hours inclusion with resolution constraints, which is valuable beyond the schema. No contradictions.

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 well-structured sentences with no fluff. Key information is front-loaded: what it returns, resolutions, usage, and extended-hours details. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations covering safety (readOnly) and output schema presumably detailing return fields, the description covers usage context, resolution options, and extended-hours behavior fully.

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% (all parameters described). The description adds nuance: 'Set extended=true (1-minute resolution only) to include premarket...'—this clarifies a constraint not fully captured in schema descriptions.

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 clearly states it fetches intraday OHLCV candles at specific resolutions (1, 5, 15, 30, 60 min). This distinguishes it from sibling tools like 'get_historical_prices' which likely provide daily or longer-term 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 explicitly recommends using this tool for 'intraday price action analysis, volume patterns, and short-term technical analysis'. It does not explicitly mention when not to use or alternatives, but the context is clear given sibling tools.

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

Deploy Server

Other Tools