Skip to main content
Glama
16Coffee

Yahoo Finance MCP Server

by 16Coffee

get_crypto_quote_short

Retrieve a concise summary of cryptocurrency market data by specifying the symbol. Access real-time prices and essential details from Yahoo Finance for informed trading decisions.

Instructions

获取指定加密货币的简要行情。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes

Implementation Reference

  • The handler function that implements the tool logic: fetches short crypto quote for a given symbol using the Financial Modeling Prep API, returns JSON string or error message.
    async def get_crypto_quote_short(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-short"
        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 short crypto quote for {symbol}: {e}"
        return json.dumps(data)
  • server.py:1142-1145 (registration)
    The @fmp_server.tool decorator that registers the get_crypto_quote_short tool with its name and description.
    @fmp_server.tool(
        name="get_crypto_quote_short",
        description="""获取指定加密货币的简要行情。""",
    )
Behavior2/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. While '获取' (get) implies a read operation, the description doesn't specify what '简要行情' (brief market data) includes, whether there are rate limits, authentication requirements, error conditions, or what format the data returns. For a tool with zero annotation coverage, this is insufficient behavioral context.

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 extremely concise - a single Chinese sentence that directly states the tool's purpose without any unnecessary words. It's appropriately sized for what it does convey, though this conciseness comes at the expense of completeness.

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?

For a tool with no annotations, no output schema, and 0% parameter schema coverage, the description is inadequate. It doesn't explain what constitutes 'brief market data', how it differs from other cryptocurrency tools, what the return format looks like, or provide any parameter guidance. The description leaves too many open questions 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.

Parameters2/5

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

The schema has 0% description coverage for its single parameter 'symbol', and the tool description provides no additional parameter information. It doesn't explain what format the symbol should be in (e.g., 'BTC', 'BTC-USD', cryptocurrency ticker format), what symbols are valid, or provide examples. With low schema coverage, the description fails to compensate for the parameter documentation 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 'brief market data for a specified cryptocurrency'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'get_crypto_quote' or 'get_crypto_price_eod', which likely offer different types of cryptocurrency 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. With multiple cryptocurrency-related sibling tools (get_crypto_quote, get_crypto_price_eod, get_crypto_intraday, etc.), there's no indication of what makes this 'brief' version different or when it should be preferred over other options.

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