Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

yahoo_finance_search

Read-only

Search Yahoo Finance for a ticker or company and return matching quotes, news, lists, and optional research reports. Use yahoo_finance_lookup to resolve one company query or yahoo_finance_ticker_quote when you already have a symbol and need only its quote.

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": {
      "Query": "<Query>"
    },
    "name": "yahoo_finance_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
QueryYesSearch query, a ticker symbol or company name, e.g. apple or AAPL. Required.
NewsCountNoMax news matches to return, default 8, max 250.
ListsCountNoMax list matches to return, default 8, max 250.
QuotesCountNoMax quote matches to return, default 8, max 250.
IncludeResearchNoInclude research reports in the results. Default false.
EnableFuzzyQueryNoEnable fuzzy matching for the query. Default false.
IncludeCulturalAssetsNoInclude cultural assets in the results. Default false.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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, covering the safety profile. The description adds useful context about the categories of results returned (quotes/news/lists/research), but discloses no auth requirements, rate limits, or pagination behavior.

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 tightly written sentences with zero waste. The core purpose is front-loaded and the sibling routing follows immediately.

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-value detail needn't be repeated. The description covers purpose and sibling routing adequately; only behavioral specifics like rate limits or auth would add more, and those are minor for a read-only search tool.

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 seven parameters with defaults and maxes. The description only hints at the query semantics ('ticker or company') and optional research reports, adding little beyond what the schema provides. Baseline 3 applies.

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 (Search) and resource (Yahoo Finance) and enumerates the result types returned: quotes, news, lists, and optional research reports. It explicitly distinguishes itself from the two named siblings yahoo_finance_lookup and yahoo_finance_ticker_quote.

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?

Names both alternatives and the conditions that select them ('resolve one company query' vs 'already have a symbol and need only its quote'). Clear routing context, though it doesn't explicitly state when this broad search is preferred over those siblings.

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

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