Local MCP

Stocks Get Chart

stocks_get_chart

Read-only

Gets historical price data for a stock symbol. Range: 1d, 5d, 1mo, 3mo, 6mo, 1y, 2y, 5y, 10y, ytd, max.

Input Schema

Name	Required	Description
`range`	No	Time range (default: 1mo)
`symbol`	Yes	Ticker symbol, e.g. AAPL
`interval`	No	Data interval (default: 1d). Intraday (1m–90m) needs a short range.

Output Schema

Name	Required	Description
`name`	No
`note`	No
`range`	No
`symbol`	No
`candles`	No
`currency`	No
`interval`	No
`change_pct`	No
`data_points`	No
`downsampled`	No	Present when the candles were thinned to the cap: {from, to} point counts.
`current_price`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026

addedOutput schema / properties / downsampled

Added value: +{
+  "description": "Present when the candles were thinned to the cap: {from, to} point counts.",
+  "type": "object"
+}

addedOutput schema / properties / note
```
Added value: +{
+  "type": "string"
+}
```

First observedJun 30, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds no behavioral context beyond that — no mention of data source, rate limits, pagination, or what interval/range combinations are valid (the schema's own note handles the latter).

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, purpose first, zero filler. The one weakness is that the range enumeration duplicates the schema enum verbatim, but it is short and does not bloat the definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and 100% parameter coverage, the description only needs to nail purpose and routing, and it half-does. It is minimally serviceable but leaves an agent guessing at the quote-vs-chart boundary and at how interval and range must be paired.

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 coverage is 100% and both enums are fully documented with defaults and the intraday-needs-short-range constraint. The description only re-lists the range enum verbatim and says nothing about 'interval' or default behavior, so it adds no meaning over the schema — baseline 3.

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?

States a specific verb+resource: 'Gets historical price data for a stock symbol.' The word 'historical' implicitly separates it from stocks_get_quote, but neither that sibling nor stocks_search_symbol is named, so the differentiation is left to the agent's inference.

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

Usage Guidelines2/5

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

There is no statement of when to use this rather than stocks_get_quote or stocks_search_symbol, and no prerequisites or exclusions. The range list describes an input, not a usage condition.

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

All Local MCP 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.