spicytrade

read_market_metrics

Read-only

Implied volatility rank, percentile and index for tracked symbols, from the public snapshot refreshed about once a minute. Sign in for the full broker metrics.

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

Input Schema

Name	Required	Description	Default
`symbols`	Yes	Ticker symbols; a leading $ cashtag is read as the bare symbol.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's added value is the data provenance: a public snapshot refreshed about once a minute, plus the fact that full broker metrics are gated behind sign-in. Those are real behavioral facts an agent needs, though error/partial-result behavior for untracked symbols is not covered.

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?

Two short sentences with zero filler, and the payload (what is returned) leads before the cadence and access caveats.

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?

For a single-parameter read tool with full schema coverage and no output schema, the description covers return contents, freshness, and access limits. Only the behavior for untracked or unsupported symbols is missing.

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 'for tracked symbols' adds a genuine constraint beyond the schema: symbols must be tracked for metrics to exist, and up to 20 are allowed by the schema. The $ cashtag handling is left entirely to the schema, which is acceptable.

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?

Names a specific verb and a precise resource: implied volatility rank, percentile and index for a set of symbols. That resource focus separates it from siblings like read_instrument_quotes or read_price_history, though no sibling is named explicitly.

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?

Usage context is only implied by 'Sign in for the full broker metrics', which signals that the public snapshot yields partial data. There is no explicit statement of when to call this versus the quote or price-history tools, and no guidance on what happens with untracked symbols.

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

All spicytrade 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.