Skip to main content
Glama

Daily prices (IEX only)

stock_prices
Read-onlyIdempotent

Daily open, high, low, close and volume of one listing of a company, newest session first, built from trades executed at IEX only. IEX is a single exchange with a small share of US volume: this is not the consolidated tape, close is the last IEX trade of the session and not the official closing price, volume is IEX volume only, and nothing is adjusted for splits or dividends. Say so when you quote a number, and show the citation in meta.attribution. For P/E, market capitalisation and other multiples use ratios_daily, which pairs each close with the facts known that day and withholds points after a likely split. ticker picks another listing of the company; from and to bound the session dates; as_of replays what was known on a date; cursor pages. Every number carries a proof naming the IEX session file it was read from.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 5,
      "company": "ticker:AAPL"
    },
    "name": "stock_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast session date, inclusive (YYYY-MM-DD).
fromNoFirst session date, inclusive (YYYY-MM-DD).
as_ofNoKnowledge date or timestamp (YYYY-MM-DD or RFC 3339). The answer is what FinancialMD knew at that instant: only facts whose known interval contains as_of. Omit for the current view.
limitNoMaximum number of periods or items to return (default 30, at most 1000).
adjustNosplits: each bar also carries split_adjusted values (confirmed splits after the session only); total_return: also total_return values, dividends reinvested at the IEX close before each ex-date (only dividends with an ex-date in the filings).none
cursorNoOpaque cursor from a previous page (data.next_cursor).
tickerNoOptional ticker of another listing of the same company (BRK.B). Default: the ticker in company, else the primary listing.
companyYesCompany identifier: a FinancialMD id ("fmd_01H..."), an SEC CIK ("cik:320193"), or a ticker ("ticker:AAPL", optionally with the MIC "ticker:AAPL.XNAS"). A bare ticker like "AAPL" is accepted and sent as ticker:AAPL. An issuer on an EU or UK regulated market that does not file with the SEC has no CIK: pass its LEI ("lei:IOG4E947OATN0KJYSD45") or its fmd_ id.

Output Schema

NameRequiredDescriptionDefault
dataNo{ items: [{ date, open, high, low, close, volume, has_broken_print }], next_cursor, listing: { ticker, mic, currency, is_primary } | null, listings, source: { id, venue, consolidated: false, adjusted: false, attribution, attribution_url, notes }, range: { from, to, sessions } }; open, high, low, close and volume are value objects. meta.attribution carries the citation the venue requires.
metaNoRequest metadata: request_id, as_of, company resolution, coverage, pipeline_version, licence, terms, proof_base.
errorNoPresent only on isError results: the API error code and message plus remedy hints.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / company / description
      Previous value: -"Company identifier: a FinancialMD id (\"fmd_01H...\"), an SEC CIK (\"cik:320193\"), or a ticker (\"ticker:AAPL\", optionally with the MIC \"ticker:AAPL.XNAS\"). A bare ticker like \"AAPL\" is accepted and sent as ticker:AAPL."New value: +"Company identifier: a FinancialMD id (\"fmd_01H...\"), an SEC CIK (\"cik:320193\"), or a ticker (\"ticker:AAPL\", optionally with the MIC \"ticker:AAPL.XNAS\"). A bare ticker like \"AAPL\" is accepted and sent as ticker:AAPL. An issuer on an EU or UK regulated market that does not file with the SEC has no CIK: pass its LEI (\"lei:IOG4E947OATN0KJYSD45\") or its fmd_ id."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Far beyond the annotations (readOnly, idempotent, non-destructive), it discloses the exchange-coverage limitation, the definition of close and volume, and the obligation to surface meta.attribution and per-number proofs. However, the unqualified claim that 'nothing is adjusted for splits or dividends' sits awkwardly against the schema's adjust parameter offering splits and total_return, so the disclosure is slightly imprecise.

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?

The critical caveat and the metasource warning are front-loaded in the first two sentences, before housekeeping about siblings and parameters. The parameter round-up sentence is dense but each clause carries information; no sentence is pure filler.

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?

With annotations, a full output schema, and 100% parameter coverage already in structured fields, the description only needs to add the interpretive constraints — and it does: data provenance, non-official close, exchange coverage, citation duty, and the multiples alternative. Nothing an agent needs to call or report this tool correctly is missing.

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 all eight parameters are already documented, and the description only briefly glosses what ticker, from/to, as_of and cursor do. It adds little meaning beyond the schema text (as_of 'replays what was known' is a mild restatement of 'knowledge date').

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?

The first sentence names a specific verb-and-resource pair (daily OHLCV bars for one listing), states ordering (newest session first) and the data source (IEX trades only). An agent can distinguish this from ratios_daily or a consolidated-tape price tool without opening 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 Guidelines5/5

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

It explicitly routes the agent away for a named use case: 'For P/E, market capitalisation and other multiples use ratios_daily.' It also defines a firm when-not boundary — this is not consolidated tape, close is not the official closing price — which tells the agent when quoting the data would be misleading.

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