Skip to main content
Glama

get_price_summary

Read-onlyIdempotent

Measure one asset's performance over a period to answer 'how did X do,' with total and annualized return, volatility, maximum drawdown dates, and data coverage.

Instructions

Measure one asset's performance over a period: total and annualized return, annualized volatility, maximum drawdown with its dates, and data coverage, all nominal and in the asset's own currency. Use it for "how did X do" questions; for one day's move ("why did it rise today") use explain_price_move. For inflation, US-dollar or gold terms use compare_real_return; for several assets use compare_assets. Ratios are fractions (0.12 means 12%).

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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoOptional ISO end date; defaults to today.
startNoOptional ISO start date, e.g. '2023-01-01'.
periodNoLookback ending at `end`. Ignored when `start` is given.1y
symbolYesA symbol returned by search_assets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.9
    • addedInput schema / properties / period / anyOf
      Added value: +[
      +  {
      +    "enum": [
      +      "1m",
      +      "3m",
      +      "6m",
      +      "ytd",
      +      "1y",
      +      "3y",
      +      "5y",
      +      "10y",
      +      "max"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / period / enum
      Removed value: -[
      -  "1m",
      -  "3m",
      -  "6m",
      -  "ytd",
      -  "1y",
      -  "3y",
      -  "5y",
      -  "10y",
      -  "max"
      -]
    • removedInput schema / properties / period / type
      Removed value: -"string"
  2. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), so the description's added value is output semantics: results are nominal and in the asset's own currency, and ratios are fractions (0.12 = 12%). That unit convention is genuinely useful for interpreting results, but it stops short of disclosing behavior around missing/partial data or latency.

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?

Front-loaded with the metric list, then routing rules, then a final unit clarification. Three tight sentences with no filler; each sentence carries distinct, load-bearing information.

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

Completeness5/5

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

No output schema exists, so the description must describe return values — and it does, naming the exact metrics and their units (nominal, own currency, ratios as fractions, drawdown dates). Combined with sibling routing, an agent has everything needed to call and interpret this tool.

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%, so the schema already documents symbol, start, end, and period (including the 'period ignored when start is given' rule). The description adds no parameter-level meaning beyond that; its unit note concerns output, not inputs. Baseline 3 is appropriate.

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?

States a specific verb ('measure') and resource (one asset's performance over a period) and enumerates the returned metrics: total and annualized return, annualized volatility, max drawdown with dates, and data coverage. It also names the sibling tools it is not (explain_price_move, compare_real_return, compare_assets), so an agent can differentiate without opening any schema.

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

Usage Guidelines5/5

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

Explicit routing: use for 'how did X do' questions; for one day's move use explain_price_move; for inflation/USD/gold terms use compare_real_return; for several assets use compare_assets. Every alternative has a clear selecting condition, leaving nothing to inference.

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