Skip to main content
Glama
rezmeplxrf

InsightSentry MCP

by rezmeplxrf

get_symbol_series

Retrieve recent historical OHLCV data for financial symbols with optional real-time updates. Configure intervals and adjustments to access up to 30,000 bars.

Instructions

Recent Time Series (up to 30k bars) with real-time data option. Retrieve recent historical OHLCV data with real-time data option for a symbol with configurable time intervals and adjustments → Returns {code: string, bar_type: string, bar_end?: number, last_update: number, series: [{time: number, open?: number, high?: number, low?: number, close: number, volume?: number, type?: string}]}. With abbr=true: {code: string, bar_type: string, bar_end?: number, last_update: number, series_keys: string[], series: number[][]} — compact arrays for reduced LLM token usage. Not all bar types include the same fields (e.g., tick data may only have [time, type, close]) — always check series_keys. For intra-day historical data (if you need more than recent 30k bars) use get_symbol_history instead. For real-time streaming, read the insightsentry://docs/websocket resource.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesSymbol in Exchange:Symbol format (e.g., NASDAQ:AAPL, NYSE:TSLA). You can search for this symbol code using the /v3/symbols/search endpoint.
bar_typeNo(Optional) Bar type. Default is 'day'
bar_intervalNo(Optional) Bar intervals. The combination of bar_type and bar_interval must not exceed one year. Default is 1.
extendedNo(Optional) Extended hours (Not all assets support extended hours). Default to true.
dadjNo(Optional) Dividend adjustment for equities and etfs (has no effect on assets without dividends). Default to false.
badjNo(Optional) Back-adjustment for continous futures contracts (has no effect on non-continous futures data). Default to true.
dpNo(Optional) Maximum number of data points to return. Higher values may increase latency. Default is 3000. Supported values: 1 - 30000
long_pollNo(Optional) If true, the server will wait up to 3 additional seconds for a real-time data before responding. Default is false.
currencyNo(Optional) Convert the OHLCV data to a different currency. The currency code must be a valid ISO 4217 currency code (e.g., USD, EUR, GBP). Do not include this field if you want to use the default currency for the symbol (Supports 173 values including: AED, AFN, ALL, AMD, AOA, ARS, AUD, AWG, AZN, BAM, ...)
settlementNo(Optional) Set Settlement as daily close. Default is false
abbrNo(Optional) Set to 'true' for compact output optimized for LLM consumption. Returns series as arrays instead of objects with a series_keys header array. Does not affect response speed — only changes the output format for reduced token usage.
filterNo(Optional) JSONata expression to filter/transform the API response server-side before it reaches you. Use this to extract only the fields or rows you need, reducing token usage. See https://jsonata.org for syntax.
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses critical behavioral traits: 30k data point limit, that abbr format 'does not affect response speed — only changes the output format,' and warns that 'Not all bar types include the same fields (e.g., tick data may only have [time, type, close]).' Could improve by stating idempotency/safety explicitly.

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?

Information-dense and well-structured: opens with scope/limit, details return formats (necessary since no output schema exists), provides data quality warnings, then sibling alternatives. Slightly verbose due to inline JSON return structure documentation, but justified given missing output schema.

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?

Excellent completeness compensating for missing output schema and annotations. Documents return structure for both abbr modes, specifies field availability variations by bar type, states explicit limits (30k bars), and provides clear migration paths to sibling tools.

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% (baseline 3). Description adds crucial semantic context: explains abbr parameter is for 'reduced LLM token usage,' links 'up to 30k bars' to dp parameter, and warns that tick bar_type has different field availability than standard OHLCV.

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?

Clear specific verb ('Retrieve') + resource ('recent historical OHLCV data') + scope ('up to 30k bars'). Explicitly distinguishes from sibling get_symbol_history by specifying the 30k bar limit vs 'more than recent 30k bars' for the alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use guidance: 'For intra-day historical data (if you need more than recent 30k bars) use get_symbol_history instead.' Also directs to websocket resource for real-time streaming, clarifying this tool's polling-based real-time option (long_poll) vs true 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/rezmeplxrf/insight_mcp'

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