Skip to main content
Glama

Signal8

by ai.signal8

Get Historical Stock Prices

get_historical_prices
Read-only

Get historical OHLCV price candles for a stock. Supports daily, weekly, and monthly resolutions. Use period shorthand (1M, 3M, 6M, 1Y, 5Y, ALL) or explicit from/to UNIX timestamps. Default is 1 year of daily candles. Use this to compute price returns, chart price history, or analyze volume trends over time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoEnd date as UNIX timestamp (overrides period)
fromNoStart date as UNIX timestamp (overrides period)
periodNoLookback period shorthand (default: "1Y"). Ignored if from/to are provided.
tickerYesStock ticker symbol (e.g., "AAPL", "TSLA")
resolutionNoCandle resolution: "D" (daily, default), "W" (weekly), "M" (monthly)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true. Description adds behavioral context: returns candle format, supports multiple resolutions, default period of 1 year. Adds value beyond annotations without contradiction.

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?

Two succinct sentences. First sentence states main purpose and resolution options. Second sentence covers period flexibility and use cases. No wasted words. Front-loaded with key info.

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?

Output schema exists, no need to explain returns. Description covers purpose, usage, parameter behavior, and example use cases. Complete for a data retrieval tool with good annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% parameter descriptions. Description adds significant extra meaning: explains period shorthand values, default behavior (1Y daily), that from/to override period, resolution default. This goes well 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 verb 'Get' and resource 'historical OHLCV price candles for a stock'. Lists supported resolutions and specific use cases (compute returns, chart, analyze volume). Distinguishes from siblings like get_intraday_bars and get_quote by specifying resolution and period options.

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?

Provides clear context for when to use: computing returns, charting, volume analysis. Explains period vs from/to timestamp usage. Doesn't explicitly exclude alternatives but given sibling count, context is sufficient.

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

All Signal8 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation3/5

Many tools have distinct purposes, but there are several groups of closely related tools (e.g., multiple insider trading and politician tools) that could cause confusion. Overall, an agent can generally distinguish tools, but the boundaries between some are fuzzy.

Naming Consistency5/5

All tool names use a consistent verb_noun pattern (get_, search_, screen_) with snake_case. This makes the tool set predictable and easy to navigate.

Tool Count1/5

With 91 tools, the server is far too large. The number of tools is excessive for a single MCP server, leading to cognitive overload and suggesting it should be split into multiple focused servers.

Completeness4/5

The tool surface covers an impressively wide domain including company data, insider trading, institutional holdings, political trading, and SEC filings. Minor gaps exist (e.g., no options or bonds), but the coverage is comprehensive for the stated purpose.

Resources