SiteCheck Crypto & Finance

Finviz quote snapshot for one stock ticker: the key

finance_finviz

Read-only

Finviz quote snapshot for one stock ticker: the key statistics table as label and value pairs (market cap, P/E, price, change, volume and similar), read from the public quote page. Values are as Finviz shows them, possibly delayed. Related tools on this server, for a different need: finance_stockanalysis when you need StockAnalysis company identity for one stock ticker; finance_bstock when you need B-Stock wholesale liquidation auctions: total live lots. 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_finviz"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes	Stock ticker, e.g. AAPL, MSFT

Output Schema

Name	Required	Description	Default
`fields`	No
`source`	No
`symbol`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the genuinely non-obvious facts that values are Finviz-displayed and possibly delayed, that pricing is $0.002 USDC per successful call via x402 across Base/Solana/Arc, and that failed calls are free. Cost and settlement-chain behavior is exactly the kind of context structured fields cannot carry.

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?

Front-loaded with the core purpose and return shape, then pricing and sibling routing. It is a single dense run-on paragraph, and the B-Stock auction sibling aside is marginal noise, but nothing is redundant enough to impair selection.

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 one-parameter read tool with a full output schema, the description covers what is returned, freshness caveats, cost model, and alternatives — everything needed to decide and invoke. Return-value detail is appropriately delegated to the output schema.

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% and the single 'symbol' parameter already carries its description and example tickers. The description reinforces the one-ticker constraint ('for one stock ticker') but adds no format, casing, or exchange-qualifier detail beyond the schema. Baseline 3 applies when the schema does the work.

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?

States a specific verb and resource: reads a Finviz quote snapshot for one ticker and returns the key statistics table as label/value pairs, with concrete example fields (market cap, P/E, price, change, volume). The scope ('one stock ticker', 'public quote page') separates it cleanly from aggregate-screener and company-identity 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?

Explicitly routes the agent to finance_stockanalysis for company identity and finance_bstock for liquidation auctions, so two alternatives are named with their selecting conditions. It does not address the many other quote-providing siblings (finance_yahoo_finance, finance_stooq_historical_stocks, finance_alpha_vantage_public), so the when-not guidance is partial rather than exhaustive.

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

All SiteCheck Crypto & Finance 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.

Resources

Need Help?