Skip to main content
Glama
narumiruna

Yahoo Finance MCP Server

get_ticker_news

Retrieve recent news articles for a specific stock symbol, including title, content, and source details, to stay informed about market developments.

Instructions

Fetches recent news articles related to a specific stock symbol with title, content, and source details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesThe stock symbol

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_ticker_news' tool, decorated with @mcp.tool() for registration in FastMCP. It takes a stock symbol, fetches the ticker using yfinance, retrieves news articles, and returns them as a string.
    @mcp.tool()
    def get_ticker_news(symbol: Annotated[str, Field(description="The stock symbol")]) -> str:
        """Fetches recent news articles related to a specific stock symbol with title, content, and source details."""
        ticker = yf.Ticker(symbol)
        news = ticker.get_news()
        return str(news)
  • The @mcp.tool() decorator registers the get_ticker_news function as an MCP tool.
    @mcp.tool()
  • Input schema defined via Annotated[str, Field(...)] for the symbol parameter; output is str.
    def get_ticker_news(symbol: Annotated[str, Field(description="The stock symbol")]) -> str:
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does, not behavioral traits. It doesn't disclose rate limits, authentication needs, data freshness, pagination, or error handling. For a tool fetching external data, this is a significant gap in transparency.

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?

The description is a single, efficient sentence with zero waste—front-loaded with the core action and resource, followed by output details. Every word earns its place, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (fetching external news), no annotations, and an output schema exists (so return values needn't be explained), the description is minimally adequate. It covers purpose and output but lacks behavioral context, making it incomplete for safe and effective use by an agent.

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% for the single parameter 'symbol', so the schema already documents it adequately. The description adds no additional meaning beyond implying the symbol is used to fetch related news, which is minimal value over the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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?

The description clearly states the action ('fetches recent news articles') and target resource ('related to a specific stock symbol'), with specific output details ('title, content, and source details'). It distinguishes from siblings like get_price_history or get_ticker_info by focusing on news rather than price data or general info, though it doesn't explicitly name alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like search (which might handle broader queries) or get_top (which might list trending stocks). The description implies usage for news about a specific symbol but lacks explicit context, prerequisites, or exclusions.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/narumiruna/yfinance-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server