market-data

Price history (OHLCV)

get_price_history

Read-onlyIdempotent

Get daily OHLCV price history for a ticker: open/high/low/close/volume. Use period_days to control how far back (default 365, max 3650).

Input Schema

TableJSON Schema

Name	Required	Description
`bars`	No	how many recent sessions to return when no window is given (default 20, max 120)
`ticker`	Yes	Ticker symbol, e.g. 'SPY', 'GDX', 'AAPL'
`to_date`	No	end of the window to quote, YYYY-MM-DD
`from_date`	No	start of the window to quote, YYYY-MM-DD
`period_days`	No	Number of days of history (default 365, max 3650)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ticker`	No
`current`	No
`date_range`	No
`total_bars`	No
`instrument_id`	No
`recent_prices`	No
`period_return_pct`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedAug 17, 2026

addedInput schema / properties / bars

Added value: +{
+  "description": "how many recent sessions to return when no window is given (default 20, max 120)",
+  "type": "integer"
+}

addedInput schema / properties / from_date

Added value: +{
+  "description": "start of the window to quote, YYYY-MM-DD",
+  "type": "string"
+}

addedInput schema / properties / to_date

Added value: +{
+  "description": "end of the window to quote, YYYY-MM-DD",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "current": {
+      "type": "object"
+    },
+    "date_range": {
+      "type": "object"
+    },
+    "instrument_id": {
+      "type": "string"
+    },
+    "period_return_pct": {
+      "type": "number"
+    },
+    "recent_prices": {
+      "items": {},
+      "type": "array"
+    },
+    "ticker": {
+      "type": "string"
+    },
+    "total_bars": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedAug 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description adds context about daily OHLCV granularity and default/max for period_days, which is useful beyond annotations. No 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 sentences, front-loaded with the core purpose, and every word contributes. No fluff or redundant explanation.

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?

Given the straightforward nature of the tool, the presence of an output schema, and complete parameter descriptions, the description is sufficiently complete for an agent to invoke it correctly. It might clarify the precedence between bars and period_days, but that is minor.

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 description coverage is 100%, so baseline is 3. The description repeats period_days default and max from the schema but adds no new meaning for bars, from_date, or to_date. It does not compensate 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?

The description clearly states 'Get daily OHLCV price history for a ticker' with specific content (open/high/low/close/volume), and this distinguishes it from sibling tools like technical indicators or sentiment data. Verb and resource are explicit.

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 gives clear context that this tool is for daily price history and provides a usage hint for the period_days parameter. However, it does not explicitly mention when to avoid this tool or name alternatives, stopping short of a 5.

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

All market-data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?