webdatatools-leads-mcp

market_quotes

Fetch live-delayed stock, ETF, index, crypto, and FX quotes in one call. Get price, change, day range, volume, and optional history without an API key.

Instructions

Live-delayed stock, ETF, index, cryptocurrency and foreign-exchange quotes in one call — price, change, day range, volume and optional history, from free public endpoints with no API key. Billed to your own Apify account: ~$0.001 per Quote (Apify free-plan price, lower on paid plans).

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": {
      "symbols": "<symbols>"
    },
    "name": "market_quotes"
  }
}

Input Schema

Name	Required	Description	Default
`symbols`	Yes	Symbols — Enter one symbol per line: a stock/ETF/index ticker (AAPL, ^GSPC), a crypto ticker or pair (BTC, BTC-USD), or an FX pair (EUR/USD, EURUSD=X, USD/EUR). Example: ["AAPL","BTC-USD","EUR/USD"].
`assetType`	No	Asset type — Choose auto to detect each symbol's type from its shape (recommended), or force every symbol in this run to be read as stock, crypto or fx. Options: auto = Auto-detect; stock = Stock / ETF / index; crypto = Cryptocurrency; fx = Foreign exchange.	auto
`historyDays`	No	History days — Enter how many days of daily closes to include in history when includeHistory is on, e.g. 30.
`includeHistory`	No	Include price history — Keep this off for a lean row per symbol. Turn it on to add a history array of daily closing prices going back historyDays days.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and discloses important traits: delayed rather than real-time data, no API key requirement, billing to the user's Apify account, and approximate per-quote cost. It omits rate limits, error behavior, and data coverage caveats, so it is strong but not exhaustive.

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

Conciseness5/5

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

The description is two well-structured sentences, front-loading what the tool does and then adding billing context. Every clause contributes useful information without repetition or filler.

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?

Given a rich input schema and no output schema, the description supplies the key return fields, data delay, source, and cost. It could elaborate slightly on output shape or symbol limits, but it is complete enough for an agent to call the tool correctly.

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 the schema already documents all four parameters thoroughly. The description only alludes to optional history and does not add syntax, constraints, or enum meaning beyond what the schema provides.

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 resource—live-delayed quotes for stocks, ETFs, indices, crypto, and FX—and specifies the scope of one call returning price, change, day range, volume, and optional history. This clearly distinguishes it from the unrelated sibling tools.

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?

The description provides useful context such as live-delayed data, free public endpoints, no API key, and Apify billing, but it does not explicitly say when to use this tool versus alternatives or when not to use it. Usage is implied rather than guided.

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

Deploy Server