Skip to main content
Glama
16Coffee

Yahoo Finance MCP Server

by 16Coffee

get_all_crypto_quotes

Retrieve bulk cryptocurrency quotes in a single request using Yahoo Finance MCP Server. Simplify access to comprehensive crypto market data for analysis and decision-making.

Instructions

获取全部加密货币的批量行情。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The asynchronous handler function for the 'get_all_crypto_quotes' tool. It retrieves batch cryptocurrency quotes from the Financial Modeling Prep API using the FMP_API_KEY environment variable and returns the data as a JSON string.
    async def get_all_crypto_quotes() -> 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/batch-crypto-quotes"
        try:
            resp = requests.get(url, params={"apikey": api_key}, timeout=10)
            resp.raise_for_status()
            data = resp.json()
        except Exception as e:
            return f"Error: getting batch crypto quotes: {e}"
        return json.dumps(data)
  • server.py:1163-1166 (registration)
    The decorator that registers the 'get_all_crypto_quotes' tool with the MCP server, specifying its name and description.
    @fmp_server.tool(
        name="get_all_crypto_quotes",
        description="""获取全部加密货币的批量行情。""",
    )
Behavior2/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 of behavioral disclosure. It states it 'gets' data, implying a read-only operation, but doesn't specify whether this is a real-time or cached query, rate limits, authentication needs, or what 'all' entails (e.g., all available cryptocurrencies or a predefined set). The description adds minimal context beyond the basic action.

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 fluff or redundancy. It's front-loaded and appropriately sized for a no-parameter tool, making it easy to parse quickly.

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?

For a tool with 0 parameters, no annotations, and no output schema, the description is minimally adequate but lacks depth. It explains what the tool does but doesn't address behavioral aspects like data freshness, scope, or error handling. Given the complexity of fetching 'all' crypto quotes, more context would be helpful, but it meets the basic threshold.

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?

The tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter details in the description. The description correctly omits parameter information, focusing on the tool's purpose. A baseline of 4 is appropriate as it doesn't mislead or add unnecessary complexity.

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 ('获取' meaning 'get') and resource ('全部加密货币的批量行情' meaning 'batch quotes for all cryptocurrencies'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_crypto_quote' or 'get_crypto_price_eod', which might offer more targeted or different types of crypto data.

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. It doesn't mention any context, prerequisites, or exclusions, leaving the agent to infer usage from the name alone. This is a significant gap given multiple crypto-related siblings exist.

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