Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_finance_search

Search Yahoo Finance by ticker symbol or company name to retrieve matching quotes, news, lists, and optional research reports for stock analysis.

Instructions

Yahoo Finance search. Searches Yahoo Finance for the required q, a ticker symbol or company name, and returns matching quotes, news and lists, plus research reports when include_research is set and Yahoo returns them. quotes_count, news_count and lists_count set how many of each; enable_fuzzy_query turns on fuzzy matching.

Input Schema

NameRequiredDescriptionDefault
qYesTicker symbol or company name
news_countNoNews result count
lists_countNoList result count
quotes_countNoQuote result count
include_researchNoInclude research reports when Yahoo returns them
enable_fuzzy_queryNoEnable fuzzy matching

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one useful conditional behavior: research reports appear only when `include_research` is set and Yahoo returns them. Beyond that it says nothing about rate limits, auth, pagination, or ordering, which for a search-style tool is a meaningful gap.

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?

Three compact sentences, front-loaded with the operation and immediately followed by inputs and outputs; no filler. It is slightly dense with parameter name-dropping, but every clause carries information.

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?

There is no output schema, so the description must convey return values, and it does name the result categories (quotes, news, lists, research). Combined with the conditional research behavior this is reasonably complete for a multi-result search tool, though pagination and result ordering are unaddressed.

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 all six parameters are already documented in the schema and the baseline is 3. The description largely restates them ('q', a ticker symbol or company name; the count params 'set how many of each'; fuzzy query 'turns on fuzzy matching') without adding format, range, or default details.

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?

States a specific verb and resource ('Searches Yahoo Finance') and enumerates concrete result categories (quotes, news, lists, and conditional research), which helps distinguish it from the ticker-specific Yahoo Finance tools. However it never names or contrasts against sibling tools like yahoo_finance_lookup or yahoo_finance_ticker_quote, so differentiation is indirect.

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 is implied by the presence of `q` (a ticker or company name) and by enumerating what comes back, so an agent can infer it is a general symbol/company lookup. There is no explicit when-to-use guidance, no statement of when to prefer this over yahoo_finance_ticker_quote, yahoo_finance_lookup, or web_search, and no exclusions.

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

Deploy Server

Other Tools