Skip to main content
Glama
myfinancialria

MyFinancial Market Data MCP

by myfinancialria
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Price History (OHLCV)

get_price_history
Read-onlyIdempotent

Retrieve daily or weekly OHLCV price history with delivery percentage for any stock. Configure lookback days, detect trends, and run technical analysis; page through truncated results using the returned cursor.

Instructions

Get OHLCV price history as row-per-day format — date, open, high, low, close, volume, delivery %. Supports configurable lookback days and daily/weekly aggregation. Default 365 days (max 2000). Use this for price analysis, trend detection, and technical calculations. IMPORTANT: days is CAPPED at 2000, so a longer request is silently shortened unless you read meta.window. Always check meta.window.truncated before treating the series as the full requested history — when it is true, meta.window.requested_days tells you what you asked for and meta.window.next_cursor gives the end_date to pass on a follow-up call to page further back. For a full multi-year series, page with end_date until truncated is false.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoNumber of days to look back (default 365, max 2000 — larger values are capped, see meta.window.truncated)
symbolNoREQUIRED. The stock symbol, e.g. "RELIANCE" or "TCS".
tickerNoAlias for `symbol`.
end_dateNoOptional YYYY-MM-DD upper bound (inclusive) for the window — the cursor for paging further back through history. Pass the `meta.window.next_cursor` from a truncated response to fetch the preceding page. Omit for the most recent window.
intervalNoBar size: "daily" (default) or "weekly" — the AGGREGATION of each row, NOT the length of the window. Use `days` for the window (e.g. days:5 for the last 5 sessions). Only end-of-day bars exist: intraday values like "1m"/"5m"/"15m"/"1h" and "monthly" are NOT supported and return an explanatory error.daily
identifierNoAlias for `symbol`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description goes beyond this by disclosing the silent 2000-day cap, the meta.window.truncated flag, and the follow-up cursor behavior. It also notes that unsupported intervals return an explanatory error, giving agents full visibility into edge cases.

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?

The description is thorough but not bloated. It is front-loaded with the core purpose and format, then addresses key caveats. Each sentence adds value, though it could be slightly more compact by merging the paging detail into one flow. Still, it is well-organized and easy to parse.

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 no output schema, the description carries the burden of explaining the return format and meta fields. It fully covers the row-per-day format, the importance of `meta.window.truncated`, and the paging mechanism. For a tool with this complexity, nothing critical is missing; an agent can confidently invoke it and interpret results.

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 coverage is 100%, yet the description adds significant meaning: it clarifies that `days` controls the window while `interval` controls aggregation, explains the `end_date` pagination cursor, and details how `meta.window` reveals truncation. It turns ambiguous schema from a potential footgun into a clear, safe pattern.

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 states a specific verb (Get) and resource (OHLCV price history), and specifies the row format (date, open, high, low, close, volume, delivery %). It clearly distinguishes this tool from siblings like get_index_history or get_live_quote by focusing on historical price data with aggregation. The purpose is unambiguous and actionable.

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?

The description explicitly recommends this tool for price analysis, trend detection, and technical calculations, and warns against unsupported intervals (intraday/monthly) that return errors. It also gives detailed pagination instructions for multi-year requests, leaving no ambiguity about when and how to use it.

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