Skip to main content
Glama
16Coffee

Yahoo Finance MCP Server

by 16Coffee

get_crypto_latest_news

Retrieve cryptocurrency news updates from the Yahoo Finance MCP Server to stay informed on market trends and developments.

Instructions

获取加密货币最新新闻列表。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
pageNo

Implementation Reference

  • The handler function that executes the tool logic: fetches latest crypto news from Financial Modeling Prep API using page and limit parameters, returns JSON string or error message.
    async def get_crypto_latest_news(page: int = 0, limit: int = 20) -> 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-latest"
        try:
            resp = requests.get(
                url,
                params={"page": page, "limit": limit, "apikey": api_key},
                timeout=10,
            )
            resp.raise_for_status()
            data = resp.json()
        except Exception as e:
            return f"Error: getting latest crypto news: {e}"
        return json.dumps(data)
  • server.py:1257-1260 (registration)
    Registers the get_crypto_latest_news tool using the @fmp_server.tool decorator with name and description.
    @fmp_server.tool(
        name="get_crypto_latest_news",
        description="""获取加密货币最新新闻列表。""",
    )
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions only the action ('获取' - get) without any information about permissions, rate limits, data freshness, pagination behavior (implied by parameters but not explained), or response format. 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 purpose. It's appropriately sized and front-loaded with no wasted words, making it easy to parse quickly.

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

Completeness2/5

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

Given the tool has 2 parameters with 0% schema coverage, no annotations, no output schema, and multiple sibling tools, the description is incomplete. It lacks essential details about parameter usage, behavioral traits, and differentiation from alternatives, making it insufficient for effective agent operation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions '列表' (list) which hints at pagination, but doesn't explain the 'limit' and 'page' parameters, their default values, valid ranges, or how they affect the news retrieval. The description adds minimal value beyond the bare schema.

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 '获取加密货币最新新闻列表' (Get the latest cryptocurrency news list) states the verb ('获取' - get) and resource ('加密货币最新新闻列表' - latest cryptocurrency news list), providing a basic purpose. However, it's vague about scope and doesn't distinguish from sibling tools like 'get_crypto_news' or 'get_stock_grade_latest_news', which could have overlapping functionality.

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

Usage Guidelines1/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. With multiple news-related sibling tools (get_crypto_news, get_stock_grade_latest_news, get_news_sentiment), the description offers no differentiation, prerequisites, or context for selection.

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