Skip to main content
Glama

get_investment_prices

Read-only

Retrieve historical investment prices for stocks, ETFs, mutual funds, and crypto to track portfolio value. Filter by ticker, date range, or price type; request full time series only when needed.

Instructions

Get investment price history for portfolio tracking. Returns one row per (security, period) for stocks, ETFs, mutual funds, and crypto. Filter by ticker symbol, date range, or price type (daily/hf). By default each row is TERSE: the security, the period, and its latest price (latest_price / latest_at) — enough to answer "what is this worth". The full price series (prices, an epoch-millis map) is most of a full row and roughly quadruples response size, so it is omitted unless requested via fields; ask for it only when you need the time series itself, not a current value.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_investment_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (default: 100, max: 10000)
fieldsNoReturn only these fields per row. Default when omitted: a terse row (security_id, ticker_symbol, price_type, date/month, latest_price, latest_at). The full intraday/daily series lives in `prices`, which is EXCLUDED by default because it is most of a row and multiplies response size several-fold — request it explicitly with fields: ["default", "prices"], or use "all" / "*" for full rows. Unknown names are omitted and reported via _field_warning.
offsetNoNumber of results to skip for pagination (default: 0)
end_dateNoEnd date (YYYY-MM-DD)
price_typeNoFilter by price type: daily (monthly aggregates) or hf (high-frequency intraday)
start_dateNoStart date (YYYY-MM-DD)
ticker_symbolNoFilter by ticker symbol (e.g., "AAPL", "BTC-USD", "VTSAX")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.0.0
    • changedInput schema / properties / end_date / description
      Previous value: -"End date (YYYY-MM-DD or YYYY-MM)"New value: +"End date (YYYY-MM-DD)"
    • addedInput schema / properties / fields
      Added value: +{
      +  "description": "Return only these fields per row. Default when omitted: a terse row (security_id, ticker_symbol, price_type, date/month, latest_price, latest_at). The full intraday/daily series lives in `prices`, which is EXCLUDED by default because it is most of a row and multiplies response size several-fold — request it explicitly with fields: [\"default\", \"prices\"], or use \"all\" / \"*\" for full rows. Unknown names are omitted and reported via _field_warning.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / start_date / description
      Previous value: -"Start date (YYYY-MM-DD or YYYY-MM)"New value: +"Start date (YYYY-MM-DD)"
  2. First observedv2.0.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint; the description goes well beyond that by disclosing default projection (terse rows), the specific fields returned, and that `prices` 'roughly quadruples response size' and is excluded unless requested. That is exactly the cost/behavior signal an agent needs before calling.

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?

Front-loaded with purpose and row shape, then the default-terse behavior, then the opt-in cost. Five sentences all carry information, though the `prices`/response-size point is restated in both the description and the schema, slightly inflating it.

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, and the description compensates fully: it describes the returned row shape, the default field set, the `latest_price`/`latest_at` semantics, and the shape of `prices` (epoch-millis map). An agent can invoke and interpret this tool from the description alone.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description still adds value by explaining the why behind `fields` (full series omitted by default, how to opt in) and by framing ticker/date/price_type as filters. Some of this duplicates the schema's own `fields` text, which keeps it from a 5.

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+resource ('Get investment price history') plus the row granularity ('one row per (security, period)') and the covered asset classes. An agent knows exactly what dataset comes back and can tell it apart from holdings/splits tools without reading the schema.

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?

Gives explicit when-to-request guidance for the expensive `prices` field: 'ask for it only when you need the time series itself, not a current value.' It does not name sibling alternatives (e.g. get_holdings for current positions), so routing between tools is left to inference.

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