Skip to main content
Glama
market-research-mcp

market-research-mcp

get_price_stats

Retrieve adjusted-close price statistics for a ticker, including 1m/3m/1y/5y returns, five-year max drawdown with peak/trough dates, 52-week high/low, and one-year annualized volatility.

Instructions

Price statistics from one provider's adjusted closes: 1m/3m/1y/5y returns (21/63/252/1260 trading days), 5-year max drawdown with peak and trough dates, 52-week high/low and 1-year annualized volatility. Descriptive only; not a recommendation.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_price_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

Output Schema

NameRequiredDescriptionDefault
as_ofYes
notesNo
staleNo
sourceYes
tickerYes
low_52wYes
returnsYes
high_52wYes
providerYes
source_urlYes
retrieved_atYes
volatility_1yYes
last_adj_closeYes
max_drawdown_5yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: adjusted closes, exact trading-day windows, max drawdown peak/trough dates, and annualized volatility. However, it leaves out important context such as which provider is used, whether ticker resolution is required, and whether adjusted-close data may differ from other price tools.

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?

The description is a single dense sentence that front-loads the resource and lists the specific computed metrics without filler. Every clause adds useful information about what is returned or how it should be interpreted.

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?

An output schema exists, so the description need not fully explain return values, and it already adds useful metric detail. Still, it lacks sibling differentiation and ticker semantics, which are relevant gaps for correct tool selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has zero description coverage and the description never mentions the ticker parameter or its expected format. For a single required parameter named ticker, the meaning is somewhat obvious, but exchange, symbol format, and resolution behavior are undocumented.

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 resource and scope: price statistics computed from one provider's adjusted closes, with returns, drawdown, 52-week range, and volatility. It is clear what the tool returns, but it does not explicitly distinguish itself from the sibling get_price_history tool.

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?

The description says the output is descriptive only and not a recommendation, which gives some context, but it provides no explicit guidance on when to use this instead of get_price_history or other price-related siblings. The agent must infer the choice from metric names alone.

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