Skip to main content
Glama

MarketWatch quote for one stock, ETF/fund or index ticker

finance_marketwatch
Read-only

MarketWatch quote for one stock, ETF/fund or index ticker (symbol, e.g. AAPL; type stock, fund or index, default stock): name, exchange, currency, last price, change and change %, quote time, plus the Key Data panel (open, day range, 52-week range, market cap, shares outstanding, float, beta, P/E, EPS, yield, dividend, ex-dividend date, short interest, average volume). Prices may be delayed. Use it when you need the valuation and dividend figures for one ticker in one call; it gives the current quote only, not price history. An unknown ticker returns 404 and is not charged. Price: $0.004 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); 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_marketwatch"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNostock, fund or index (default stock; use fund for ETFs/mutual funds)
symbolYesTicker, e.g. AAPL, MSFT, SPY

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses delay characteristics ('Prices may be delayed'), failure semantics ('unknown ticker returns 404 and is not charged'), and full cost/payment mechanics ($0.004 per successful call via x402 on USDC/Base and other networks, failures free). Those are exactly the traits an agent needs before spending money.

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?

Everything is delivered in one front-loaded paragraph with the resource and parameters first, then the return payload, then usage, then cost. The long field enumeration is dense but earns its place by signalling available valuation data; minor trimming of the dividend/short-interest list would tighten it further.

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?

For a paid, read-only, single-ticker quote tool with an output schema already present, the definition covers scope, return contents, latency caveat, error behavior, and pricing. Nothing an agent needs in order to call it correctly or decide whether to call it 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 both parameters are already documented, and the description largely restates the schema's 'stock, fund or index (default stock)' wording. It adds only a small clarification that 'fund' covers ETFs and mutual funds; the baseline of 3 applies when the schema carries the load.

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 uses a specific verb+resource pair ('MarketWatch quote for one stock, ETF/fund or index ticker') and enumerates exactly what the call returns, including the Key Data panel fields. An agent can immediately tell this is a single-ticker snapshot lookup rather than a screener or history tool.

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 states the positive case ('use it when you need the valuation and dividend figures for one ticker in one call') and an explicit exclusion ('it gives the current quote only, not price history'). The alternative for historical data is named by category, which is enough to route the agent away.

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