Skip to main content
Glama

Interactive Price Chart

price_chart
Read-only

Render an interactive candlestick chart for a symbol inside the conversation. Accepts crypto pairs (BTCUSDT, BTC-USD), stocks (AAPL, NVDA) or any Yahoo Finance symbol. period: 1mo|3mo|6mo|1y|2y (1h also takes 1d|5d), interval: 1d|1h|15m. 15m charts show recent action only: period is limited to 1d|5d|1mo (longer values auto-adjust to 5d) and the most recent 350 bars are drawn. Set bollinger=true to overlay Bollinger Bands (SMA20 ± 2σ); the latest band values are returned in the result. Clients without interactive app support can read the summary field of the result.

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": "price_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNo6mo
symbolYes
intervalNo1d
bollingerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the bar is lower, yet the description still adds real behavior: the 350-bar draw cap for 15m, automatic period adjustment, Bollinger overlay semantics (SMA20 ± 2σ) and that band values come back in the result, plus the `summary` fallback field. The only gap is that it does not say what happens if the symbol cannot be resolved or how the chart payload is structured.

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?

It is a dense single block, but each sentence carries information: first the purpose, then symbol domain, then constraints on period/interval, then bollinger semantics, then the client fallback. Readability would improve with separators or bullets around the constraint clauses, but nothing is padded or redundant.

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?

With four parameters, no output schema, and zero schema descriptions, the description supplies nearly everything an agent needs: value domains, defaults implicitly handled by the schema, rendering limits, and how to read results without app support. Only error behavior for unresolvable symbols and any latency/render caveats are left unstated.

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 description coverage is 0% and the schema declares no enums, so the description carries the full burden — and it does: allowed values for period (1mo|3mo|6mo|1y|2y, with 1d|5d available for 1h), interval (1d|1h|15m), the meaning of bollinger, and the accepted symbol formats. Meaning is added beyond the bare types for every parameter.

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?

"Render an interactive candlestick chart for a symbol inside the conversation" gives a specific verb (render) plus resource (candlestick chart) and states the delivery surface (inside the conversation), which cleanly separates it from data-returning siblings like yahoo_price and from backtest_chart. The accepted symbol space (crypto pairs, stocks, Yahoo symbols) further pins down its scope.

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?

It provides concrete usage rules: supported symbol formats, allowed period/interval values, the 15m restriction with its auto-adjust to 5d behavior, and a fallback for clients without interactive app support. It does not explicitly say when to pick this over a sibling that also returns price data, but the modality guidance is clear enough that an agent knows the conditions for calling it.

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.