Skip to main content
Glama
16Coffee

Yahoo Finance MCP Server

by 16Coffee
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_crypto_news

Search for cryptocurrency-related news by providing specific crypto symbols. This tool connects to the Yahoo Finance MCP Server to deliver targeted financial updates.

Instructions

搜索加密货币相关新闻。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolsYes

Implementation Reference

  • server.py:1240-1254 (handler)
    The main handler function that fetches cryptocurrency news from the Financial Modeling Prep API using the provided symbols, handles errors, and returns JSON data.
    async def get_crypto_news(symbols: str) -> str:
    """获取加密货币新闻"""

    api_key = os.environ.get("FMP_API_KEY")
    if not api_key:
        return "Error: FMP_API_KEY environment variable not set."

    url = "https://financialmodelingprep.com/stable/news/crypto"
    try:
        resp = requests.get(url, params={"symbols": symbols, "apikey": api_key}, timeout=10)
        resp.raise_for_status()
        data = resp.json()
    except Exception as e:
        return f"Error: getting crypto news for {symbols}: {e}"
    return json.dumps(data)
  • server.py:1236-1239 (registration)
    The decorator that registers the 'get_crypto_news' tool with the MCP server, including its name and description.
    @fmp_server.tool(
    name="get_crypto_news",
    description="""搜索加密货币相关新闻。""",
)

Tool Definition Quality

C2.1/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. It doesn't indicate whether this is a read-only operation, how results are returned (e.g., pagination, format), rate limits, authentication needs, or any side effects. This is inadequate for a tool with parameters and no output schema.

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 in Chinese ('搜索加密货币相关新闻') that directly states the tool's function without any unnecessary words. It's front-loaded and appropriately sized for its minimal content.

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

Completeness1/5

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

Given the tool has one required parameter with 0% schema coverage, no annotations, no output schema, and multiple sibling tools (e.g., 'get_crypto_latest_news'), the description is severely incomplete. It fails to explain parameter usage, differentiate from siblings, or describe behavioral aspects, making it inadequate for effective tool selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning the parameter 'symbols' is undocumented in the schema. The description adds no information about what 'symbols' represents (e.g., cryptocurrency tickers like BTC, ETH), expected format, or how it influences the search. This leaves the parameter's meaning and usage completely unclear.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '搜索加密货币相关新闻' (Search for cryptocurrency-related news) clearly states the action (search) and resource (cryptocurrency news), making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'get_crypto_latest_news', leaving ambiguity about whether this searches historical news or provides the latest updates.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_crypto_latest_news' or 'get_news_sentiment'. It mentions no prerequisites, exclusions, or specific contexts, leaving the agent to infer usage based solely on the tool name and description.

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/16Coffee/finance-mcp'

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