Skip to main content
Glama

SiteCheck Crypto & Finance

Real-time US stock, ETF or index quote: company name

finance_iex_cloud_public
Read-only

Real-time US stock, ETF or index quote (replacement for the closed IEX Cloud public quote): company name, exchange, last sale price, net and % change, bid/ask price and size, volume, last trade time, market status (pre-market, open, after-hours, closed) with the regular-session close, day high/low, 52-week range and upcoming earnings date. Data from Nasdaq.com's public quote API. Related tools on this server, for a different need: finance_alpha_vantage_public when you need Alpha Vantage global quote for one stock or ETF ticker; crypto_etherscan_label_cloud when you need Etherscan public address-label cloud: entity labels. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": "finance_iex_cloud_public"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesUS ticker, e.g. AAPL, MSFT, SPY
assetClassNostock (default), etf or index

Output Schema

NameRequiredDescriptionDefault
nameNo
quoteNo
sourceNo
symbolNo
dayRangeNo
exchangeNo
checkedAtNo
assetClassNo
marketStatusNo
nextEarningsNo
fiftyTwoWeekRangeNo
regularSessionCloseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only supply readOnlyHint and openWorldHint, so the description adds real value: the upstream source is Nasdaq.com's public quote API, pricing is $0.002 in USDC per successful call via x402 on Base, Solana or Arc, and failed calls are not charged. This billing behavior is essential and not derivable from structured fields; only rate limits or latency are absent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The tool's core purpose is front-loaded in the first clause, but the definition is one very long sentence that bundles a field list, sibling routing, provenance and pricing together. The crypto_etherscan_label_cloud cross-reference does not earn its place for a US equity quote tool and dilutes the routing signal.

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?

With an output schema present, the description need not explain return values, yet it briefly enumerates them, and it covers cost, payment rails, data source and scope. For a two-parameter read-only quote tool this is sufficient; only freshness or rate-limit expectations are unstated.

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% with only two parameters, so the baseline is 3. The description does confirm that stock, ETF and index are all supported, which corroborates the assetClass parameter, but it adds no format, default or edge-case guidance beyond the schema's own examples (AAPL, MSFT, SPY).

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 states a specific verb and resource (real-time quote) and enumerates exactly what is returned: last sale price, bid/ask with size, volume, market status, day range, 52-week range and earnings date. It also scopes the coverage to US stock, ETF or index, which is enough for an agent to distinguish it from the broad crypto/price-feed siblings.

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 explicitly routes to finance_alpha_vantage_public when an Alpha Vantage global quote for a single stock or ETF ticker is wanted, and names crypto_etherscan_label_cloud for address labels. The context for using this tool (US real-time quote) is clear, but there are no explicit exclusions such as non-US listings, and the etherscan reference is not a plausible alternative for this need.

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