Skip to main content
Glama

Live Stock Quote

GetLiveQuote
Read-only

Get the latest intraday reading for active U.S. listings (consolidated SIP: last trade, UTC time, freshness, bid/ask, the trade's session (pre-market, regular, after hours), the regular close once settled, change from the previous close and day volume) and for listings named MIC:TICKER on a Canadian exchange (XTSE, XTSX, XCNQ, NEOE; e.g. XTSE:RY), Euronext (XPAR, XAMS, XBRU, XMSM, XOSL, MTAA, XLIS; e.g. XPAR:AIR), NSE (XNSE; e.g. XNSE:RELIANCE) or BSE (XBOM, BSE-only companies), in the listing's currency. Needs a paid plan: U.S. is real time on Pro, 15 minutes delayed on Plus; Canadian is real time on XTSE and XTSX, 15 minutes behind on XCNQ and NEOE; Euronext trails 15 minutes (Delayed=true); Indian readings come from the exchange on request with its own time (Delayed=true when trailing). Free gets an upgrade note. Stale=true: the reading predates the session expected now and is not current. Missing readings are listed. Settled daily bars: GetLatestClosingPrices or GetStockPrices.

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": {
      "tickers": "<tickers>"
    },
    "name": "GetLiveQuote"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickersYesTicker symbols (max 25): a bare ticker for a U.S. listing, MIC:TICKER for a Canadian, Euronext, NSE or BSE one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / tickers / description
      Previous value: -"Ticker symbols (max 25): a bare ticker for a U.S. listing, MIC:TICKER for a Canadian, Euronext or NSE one."New value: +"Ticker symbols (max 25): a bare ticker for a U.S. listing, MIC:TICKER for a Canadian, Euronext, NSE or BSE one."
  2. Changed1 schema field changed
    • changedInput schema / properties / tickers / description
      Previous value: -"Ticker symbols (max 25): a bare ticker for a U.S. listing, MIC:TICKER for a Canadian or Euronext one."New value: +"Ticker symbols (max 25): a bare ticker for a U.S. listing, MIC:TICKER for a Canadian, Euronext or NSE one."
  3. Changed1 schema field changed
    • changedInput schema / properties / tickers / description
      Previous value: -"Ticker symbols (max 25): a bare ticker for a U.S. listing, MIC:TICKER for a Canadian one."New value: +"Ticker symbols (max 25): a bare ticker for a U.S. listing, MIC:TICKER for a Canadian or Euronext one."
  4. Changed1 schema field changed
    • changedInput schema / properties / tickers / description
      Previous value: -"Ticker symbols (max 25)."New value: +"Ticker symbols (max 25): a bare ticker for a U.S. listing, MIC:TICKER for a Canadian one."
  5. Changed3 schema fields changed
    • changedInput schema / properties / tickers / description
      Previous value: -"One ticker (e.g. AAPL) or a comma-separated list (e.g. AAPL,MSFT,NVDA), max 25."New value: +"Ticker symbols (max 25)."
    • addedInput schema / properties / tickers / items
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / tickers / type
      Previous value: -"string"New value: +"array"
  6. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful behavior beyond them: latency by plan and exchange, the meaning of Delayed=true and Stale=true, missing readings being listed, per-listing currency, and a Free-tier upgrade note. It does not describe pagination, batching limits beyond the schema's 25, or rate limiting, so it stays short of the top score for a data-fetch tool.

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?

It is front-loaded: the returned fields come first, then the market/plan matrix, then the stale/missing semantics and alternatives. The dense parenthetical enumeration of every exchange code is verbose but functional, since those codes are needed to build valid tickers.

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?

There is no output schema, so the description carries the full burden of describing return values, and it does so field by field (last trade, UTC time, freshness, bid/ask, session, settled close, change, volume). Combined with the delay/staleness semantics and the alternative for settled bars, nothing material is missing for a single-parameter quote tool.

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 the baseline is 3, but the description goes further by defining the MIC:TICKER addressing convention and giving concrete examples (XTSE:RY, XPAR:AIR, XNSE:RELIANCE), plus the accepted exchange codes. It also states that values come back in the listing's own currency, which the schema does not.

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 description names a specific verb and resource ('latest intraday reading') and enumerates the exact fields returned, then scopes it by market (U.S. SIP plus named Canadian, Euronext, NSE and BSE venues). It explicitly contrasts itself with settled daily bars, so an agent can distinguish it from GetLatestClosingPrices/GetStockPrices without opening another 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?

It gives a clear use case (current intraday quote) and routes the agent away to a named alternative for settled daily bars. It also explains plan-tier preconditions that determine whether a call is even worthwhile (Pro/Plus/Free for U.S., per-exchange delays for Canada, Euronext and India). It does not address other intraday alternatives such as GetIntradayStockPrices, leaving some ambiguity about which intraday tool to pick.

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.