Skip to main content
Glama
16Coffee

Yahoo Finance MCP Server

by 16Coffee

get_crypto_quote

Retrieve complete market data for any specified cryptocurrency, including price, volume, and trends, using Yahoo Finance MCP Server.

Instructions

获取指定加密货币的完整行情。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes

Implementation Reference

  • The handler function that implements the get_crypto_quote tool. It retrieves the crypto quote for a given symbol from the Financial Modeling Prep API, handles API key, makes HTTP request, and returns JSON data or error.
    async def get_crypto_quote(symbol: 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/quote"
        try:
            resp = requests.get(url, params={"symbol": symbol, "apikey": api_key}, timeout=10)
            resp.raise_for_status()
            data = resp.json()
        except Exception as e:
            return f"Error: getting crypto quote for {symbol}: {e}"
        return json.dumps(data)
  • server.py:1121-1124 (registration)
    The registration of the get_crypto_quote tool via the @fmp_server.tool decorator, defining its name and description.
    @fmp_server.tool(
        name="get_crypto_quote",
        description="""获取指定加密货币的完整行情。""",
    )
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it retrieves '完整行情' (complete market data), which implies a read-only operation, but doesn't specify what 'complete' includes, whether there are rate limits, authentication requirements, error conditions, or response format. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 that gets straight to the point with no wasted words. It's appropriately sized for a simple tool with one parameter and is front-loaded with the core purpose.

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 lack of annotations, no output schema, and 0% schema description coverage, the description is insufficiently complete. It doesn't explain what '完整行情' includes, how the data is structured, or any operational constraints, leaving the agent with inadequate context for reliable tool invocation.

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?

The description mentions '指定加密货币' (specified cryptocurrency), which aligns with the 'symbol' parameter in the schema. However, with 0% schema description coverage, the description doesn't add meaningful details about parameter format, examples, or constraints beyond what's implied. It compensates minimally for the schema gap.

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 'complete market data for specified cryptocurrency'), making the purpose immediately understandable. It doesn't explicitly distinguish from sibling tools like 'get_crypto_quote_short' or 'get_crypto_price_eod', which would require more specific differentiation.

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_quote_short' or 'get_crypto_price_eod'. There's no mention of prerequisites, context, or comparison with sibling tools, leaving the agent to infer usage from tool names alone.

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