Skip to main content
Glama

Valeur Intrinsèque

get_price_history

Price-history summary for one ticker: first and last price, change, high, low, and the last 10 points. Not counted in the Score VI quota.

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
rangeNoHistory window (default: 1y)1y
symbolYesStock ticker or company name (e.g. AAPL, LVMH)
intervalNoBar interval (default: 1d)1d

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 it does disclose the returned summary fields and a quota behavior (not counted against Score VI), which is genuinely useful. It omits other behavior: whether the call is purely read-only, how the 'last 10 points' relate to the chosen interval, and what happens for an unknown symbol.

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?

Two short sentences, front-loaded with the resource and its outputs, with no filler. The trailing quota sentence is terse but somewhat opaque jargon that costs a little clarity.

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 three well-documented parameters and no output schema, the description must describe return values and does so adequately for the aggregate statistics. It falls short on the 'last 10 points' wording, which is ambiguous given configurable range and interval, and it gives no guidance on choosing it over siblings.

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% and both enums (range, interval) are documented in the schema, so the baseline is 3. The description adds no extra meaning about how range and interval interact with the reported summary window.

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 (price-history summary for one ticker) and enumerates the returned fields, so an agent knows exactly what it gets. It does not explicitly contrast itself with the sibling get_stock_price, so sibling 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 Guidelines2/5

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

There is no when-to-use guidance at all: nothing says whether to prefer this over get_stock_price or analyze_stock, nor whether it should be called only after resolving a ticker. The second sentence about the Score VI quota is a cost aside, not usage guidance.

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