Crawlora MCP

yahoo_finance_screener

Read-only

Fetch quote rows from a predefined Yahoo Finance screener. Use yahoo_finance_screeners to discover supported screen IDs, or yahoo_finance_screener_custom when you need to supply custom filters.

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": {
      "id": "<id>"
    },
    "name": "yahoo_finance_screener"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Predefined screener id.
`count`	No	Result count.
`offset`	No	Result offset.
`sort_asc`	No	Sort ascending.
`sort_field`	No	Sort field for offset/customized runs.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and network behavior are covered. The description adds the useful constraint that the screener must be predefined, but says nothing about pagination semantics (count/offset) or result volume limits beyond what the schema implies. With annotations carrying the safety profile, this is adequate but not rich.

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 tight sentences with no waste, and the core action is front-loaded ahead of the routing guidance.

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?

An output schema exists, so return values need not be explained, and the routing to sibling tools is complete. Minor gap: pagination/result-window behavior for count and offset is left entirely to the 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 description coverage is 100%, so every parameter is already documented in the schema. The description adds only the 'predefined' qualifier on id and no detail on count, offset, or sort behavior. Baseline 3 is correct when the schema does the heavy lifting.

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 ('Fetch quote rows from a predefined Yahoo Finance screener') and immediately contrasts with the sibling tools that handle discovery and custom filtering. An agent can distinguish this from yahoo_finance_screener_custom and yahoo_finance_screeners without opening any schema.

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?

Explicitly routes: use yahoo_finance_screeners to discover IDs, and yahoo_finance_screener_custom when custom filters are needed. This names both alternatives and the condition selecting each, leaving nothing to inference.

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

All Crawlora MCP 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?