Skip to main content
Glama

Price history

get_price_history
Read-onlyIdempotent

Daily (or intraday for 1D and 5D) price history for one symbol over a range, with the period return, high and low. Returns up to 400 points.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeNoOne of 1D, 5D, 1M, 3M, 6M, YTD, 1Y, 2Y, 5Y, 10Y, MAX. Default 6M.
symbolYesTicker symbol, e.g. NVDA, SPY or BRK.B. Index symbols use ^, e.g. ^GSPC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the description's added value is the granularity rule (daily, or intraday for 1D/5D) and the hard cap of 400 returned points. Those are real behavioral constraints a caller needs to plan a request, though nothing is said about trimming/resampling when a range would exceed 400 points.

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?

A single dense sentence with the resource and granularity rule front-loaded and the point cap at the end. Every clause carries information; nothing is padding.

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?

For a two-parameter, read-only tool with no output schema, the definition covers what the series contains (return, high, low) and the size limit. It leaves the per-point shape (e.g. OHLC vs close-only) and any adjustment conventions unstated, which is a modest remaining gap.

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%, so both parameters are already documented, but the description adds meaning the schema does not: that the range value also controls data granularity. It does not elaborate on symbol formats, but the schema already covers those with examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The definition names a specific verb and resource ('price history for one symbol over a range') and specifies the output payload (period return, high, low). It implicitly separates itself from quote/snapshot siblings by being a ranged time series, but never names an alternative, so the differentiation is left to inference.

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

Usage Guidelines3/5

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

Usage is only implied: the caller can infer this is the tool for a historical series and that 1D/5D yields intraday granularity. There is no explicit guidance on when to prefer get_quotes or get_stock_snapshot, and no stated exclusions or prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources