Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

yahoo_finance_ticker_news

Retrieve stock ticker news by symbol, with optional count and tab filters for news, all, or press releases.

Instructions

Yahoo Finance ticker news. Returns the Yahoo Finance news stream for the ticker in the symbol path parameter, such as AAPL. count limits the items (default 8, max 250) and tab picks news (default), all or press_releases. Stories have title, provider, dates and URLs. A valid empty stream returns news: [].

Input Schema

NameRequiredDescriptionDefault
tabNoNews tab: news, all, or press_releases
countNoNews result count
symbolYesYahoo Finance symbol such as AAPL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the default (8) and maximum (250) counts, the default tab, and crucially the empty-stream behavior ('news: []'), which prevents an agent from misreading an empty result as an error. It omits auth/rate-limit or ordering details, so not a 5.

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?

Four short sentences, front-loaded with the purpose, then parameters, then return shape and the empty case. No filler; every sentence adds either scoping, defaults or output expectations.

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?

No output schema and no annotations, so the description must cover return expectations, and it does by naming the story fields (title, provider, dates, URLs) and the empty-stream case. For a simple read-only stream fetcher this is nearly complete, with only minor gaps around ordering or auth.

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 schema baseline is 3, but the description adds the default for count (8) and its cap (250), plus the default tab value ('news'), none of which appear in the terse schema descriptions. That is meaningful added semantics for count and tab, though the symbol format is only restated ('AAPL').

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 ('Returns') and resource ('Yahoo Finance news stream for the ticker'), naming the exact path parameter and an example value. An agent can distinguish it from sibling ticker tools like yahoo_finance_ticker_options or yahoo_finance_ticker_info without opening the schema.

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?

The tab enumeration gives implied usage context (news vs all vs press_releases) and defaults for count and tab, which helps orient the agent. However, it never states when to prefer this tool over alternatives such as yahoo_search_news or yahoo_news_* siblings, and names 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