Skip to main content
Glama

Leeway Financial Data

prices

prices
Read-only

Prices for SYMBOL.EXCHANGE. view=eod is daily OHLCV. view=live is the latest quote. view=intraday is 1m, 5m, or 1h bars; pass interval. For a fund whose management company publishes its data, ISIN.NAV is the daily net asset value: close is the NAV, adjusted_close includes reinvested distributions, there is no intraday. For whether today's move is unusual, use prices_relative_move.

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": {
      "view": "<view>",
      "symbolExchange": "<symbolExchange>"
    },
    "name": "prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoYYYY-MM-DD. The end date, if not provided, today in 7 days will be used.
fromNoFormat: YYYY-MM-DD. The start date, if not provided, today will be used.
viewYeseod is daily bars. live is the latest quote. intraday is intraday bars.
multiNoOptional: Comma-separated list of additional SYMBOL.EXCHANGE tickers. Response is an array when provided.. Example: SAP.XETRA,EURUSD.FOREX
bynameNoSet this to true and pass a Companyname in symbolExchange.
filterNoSet this to e.g. close to get only ONE (e.g. close) for each day. Date is always returned. Keys are renamed to time,value
intervalNo'5m' for 5 minutes, '1h' for 1 hour, and '1m' for 1 minute intervals. 1 minute is only available for US exchanges NYSE and NASDAQ.
symbolExchangeYesSymbol and Exchange. Example: SAP.XETRA

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description's real contribution is the fund/ISIN variant where close equals NAV, adjusted_close includes reinvested distributions, and intraday is unavailable. It says nothing about rate limits, pagination, gaps in data, or the shape of the response array when multi is used. Adding the multi/byname behavioral consequences (array vs object) would have raised this above a 3.

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?

Four dense, front-loaded sentences that move from core resource to view semantics to the fund special case to the alternative tool; no filler. The telegraphic style ("view=intraday is 1m, 5m, or 1h bars; pass interval") is efficient but borders on fragmentary.

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?

For an 8-parameter, read-only, open-world query tool with no output schema, the description covers the semantics that matter (view behavior, fund NAV caveat, alternative tool). It leaves response shape for multi/filter results and date-window defaults to the schema, which is a modest gap.

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 coverage is 100%, so the baseline is 3, and most of the description's view/interval wording restates the enum descriptions in the schema. The genuine addition is the ISIN.NAV form for symbolExchange and the view-to-interval dependency, but multi, filter, byname, from and to are covered only by the schema.

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?

Names the resource and its addressing key ("Prices for SYMBOL.EXCHANGE") and then enumerates what each view returns (eod=OHLCV, live=latest quote, intraday=bars), which lets an agent distinguish it from prices_relative_move and from quote-style siblings. Lacks a crisp verb, but the scope and output semantics are specific enough to act on.

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 concrete selection rules between the three views and the interval requirement for intraday, plus an explicit alternative ("For whether today's move is unusual, use prices_relative_move"). It adds a valuable routing rule for funds (ISIN.NAV rather than SYMBOL.EXCHANGE), but states no exclusions or failure conditions, so a 4 rather than 5.

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