Wealthnow

Market data tools

market_data_tools

Read-onlyIdempotent

Quotes, charts, ETF holdings and crypto market feeds (funding, open interest, basis, on-chain flows). Use it for a stock's or coin's current price, a chart or an ETF's holdings. Pick one of its 13 operations in operation and pass its arguments in arguments.

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": {
      "operation": "<operation>"
    },
    "name": "market_data_tools"
  }
}

Input Schema

Name	Required	Description	Default
`arguments`	No	The operation's own arguments, by the names its line gives. search_tools returns any operation's full inputSchema.
`operation`	Yes	The operation to run. One line each: name(its arguments, * = required): what it does. crypto_derivatives_basis(symbols, asset_class, detail): Call this to read CARRY: perpetual premium (mark vs oracle/index) in basis points per venue read first-party, and the cross-venue mean crypto_derivatives_funding(symbols, asset_class, detail): Call this when you need to know whether a coin's perp market is CROWDED crypto_derivatives_open_interest(symbols, asset_class, detail): Call this for LEVERAGE in the system crypto_derivatives_vol_surface(symbol, asset_class): Call this for the OPTIONS market's view crypto_events_announcements(hours, event_type, symbols, asset_class): Call this to know WHAT an exchange announced and WHEN crypto_events_headlines(limit, event_type, symbols, tier1_only, asset_class): Call this for what is BREAKING on crypto-native social and blogs right now, already mapped to coins crypto_onchain_flows(hours, asset_class): Stablecoin issuance and lending liquidations read straight off the chain; use it for on-chain liquidity and deleveraging crypto_quote(ticker, vs, series, asset_class): Live crypto quote from the market-data feed (real-time entitlement) crypto_universe(limit, offset, min_dollar_volume, asset_class): The full liquid crypto universe: every priced USD pair that clears a dollar-volume floor (default $1M a day), ranked by dollar volume, stablecoins excluded intel_chart(ticker, interval, bars, indicators): Candlestick chart with optional RSI/MACD/Bollinger overlays intel_etf_holdings(etf, ticker, limit): An ETF's holdings with their weights, or which covered ETFs hold a stock: use it when asked what a fund owns or which funds own a name intel_etf_summary(ticker): One-call ETF intelligence rollup: top holdings + commodity exposure + which other v3 tools work for this ticker market_quote(ticker): Level 1 quote for one ticker from live market data: last print, bid/ask when the session has a book, sizes, day volume, prev_close, change

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedInput schema / properties / operation / description

Previous value: -"The operation to run. One line each: name(its arguments, * = required): what it does.\ncrypto_derivatives_basis(symbols, asset_class, detail): Call this to read CARRY: perpetual premium (mark vs oracle/index) in basis points per venue read first-party, and the cross-venue mean\ncrypto_derivatives_funding(symbols, asset_class, detail): Call this when you need to know whether a coin's perp market is CROWDED\ncrypto_derivatives_open_interest(symbols, asset_class, detail): Call this for LEVERAGE in the system\ncrypto_derivatives_vol_surface(symbol, asset_class): Call this for the OPTIONS market's view\ncrypto_events_announcements(hours, event_type, symbols, asset_class): Call this to know WHAT an exchange announced and WHEN\ncrypto_events_headlines(limit, event_type, symbols, tier1_only, asset_class): Call this for what is BREAKING on crypto-native social and blogs right now, already mapped to coins\ncrypto_onchain_flows(hours, asset_class): Stablecoin issuance and lending liquidations read straight off the chain; use it for on-chain liquidity and deleveraging\ncrypto_quote(ticker*, vs, series, asset_class): Live crypto quote from the market-data feed (real-time entitlement)\ncrypto_universe(limit, offset, min_dollar_volume, asset_class): The full liquid crypto universe: every priced USD pair that clears a dollar-volume floor (default $1M a day), ranked by dollar volume, stablecoins excluded\nintel_chart(ticker*, interval, bars, indicators): Candlestick chart with optional RSI/MACD/Bollinger overlays\nintel_etf_holdings(etf, ticker, limit): An ETF's holdings with their weights, or which covered ETFs hold a stock: use it when asked what a fund owns or which funds own a name\nintel_etf_summary(ticker*): One-call ETF intelligence rollup: top holdings + commodity exposure + which other v3 tools work for this ticker\nmarket_quote(ticker*): L1 quote for one ticker via the live vendor_fallback path: last print, bid/ask when the session has a book, sizes, day volume, prev_close, change"New value: +"The operation to run. One line each: name(its arguments, * = required): what it does.\ncrypto_derivatives_basis(symbols, asset_class, detail): Call this to read CARRY: perpetual premium (mark vs oracle/index) in basis points per venue read first-party, and the cross-venue mean\ncrypto_derivatives_funding(symbols, asset_class, detail): Call this when you need to know whether a coin's perp market is CROWDED\ncrypto_derivatives_open_interest(symbols, asset_class, detail): Call this for LEVERAGE in the system\ncrypto_derivatives_vol_surface(symbol, asset_class): Call this for the OPTIONS market's view\ncrypto_events_announcements(hours, event_type, symbols, asset_class): Call this to know WHAT an exchange announced and WHEN\ncrypto_events_headlines(limit, event_type, symbols, tier1_only, asset_class): Call this for what is BREAKING on crypto-native social and blogs right now, already mapped to coins\ncrypto_onchain_flows(hours, asset_class): Stablecoin issuance and lending liquidations read straight off the chain; use it for on-chain liquidity and deleveraging\ncrypto_quote(ticker*, vs, series, asset_class): Live crypto quote from the market-data feed (real-time entitlement)\ncrypto_universe(limit, offset, min_dollar_volume, asset_class): The full liquid crypto universe: every priced USD pair that clears a dollar-volume floor (default $1M a day), ranked by dollar volume, stablecoins excluded\nintel_chart(ticker*, interval, bars, indicators): Candlestick chart with optional RSI/MACD/Bollinger overlays\nintel_etf_holdings(etf, ticker, limit): An ETF's holdings with their weights, or which covered ETFs hold a stock: use it when asked what a fund owns or which funds own a name\nintel_etf_summary(ticker*): One-call ETF intelligence rollup: top holdings + commodity exposure + which other v3 tools work for this ticker\nmarket_quote(ticker*): Level 1 quote for one ticker from live market data: last print, bid/ask when the session has a book, sizes, day volume, prev_close, change"

First observedOct 21, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that this is a read-oriented market-data gateway with 13 operations, but it does not add details on data freshness, entitlements, rate limits, or error behavior.

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 description is three short sentences and front-loads the resource categories before explaining how to call the tool. It is efficient, though the phrase 'Pick one of its 13 operations' could be tighter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 13-operation dispatcher, the top-level description names only broad categories and omits operations like events, vol surface, universe, and ETF summary. The rich enum schema compensates for much of this, so the description is adequate but not complete on its own.

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%, and the enum description documents each operation with its own argument names. The tool description only restates the routing pattern: choose an operation and pass its arguments in 'arguments'. That is useful but adds little beyond 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?

The description states specific resource categories (quotes, charts, ETF holdings, crypto feeds) and frames the tool as a dispatcher across 13 operations, so the purpose is clear. It does not explicitly distinguish this gateway from sibling tools such as crypto_market_tools or funds_tools, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It gives positive usage examples: current price, chart, or ETF holdings. However, the top-level description provides no when-not guidance or alternatives to sibling tools, leaving routing decisions partly to inference.

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

All Wealthnow tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.