Skip to main content
Glama
financial-datasets

Financial Datasets MCP Server

Official

get_available_crypto_tickers

Retrieve all available cryptocurrency ticker symbols for accessing market data through the Financial Datasets MCP Server.

Instructions

Gets all available crypto tickers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_available_crypto_tickers' tool. It is registered via the @mcp.tool() decorator. Fetches available crypto tickers from the Financial Datasets API endpoint and returns them as a JSON string.
    @mcp.tool()
    async def get_available_crypto_tickers() -> str:
        """
        Gets all available crypto tickers.
        """
        # Fetch data from the API
        url = f"{FINANCIAL_DATASETS_API_BASE}/crypto/prices/tickers"
        data = await make_request(url)
    
        # Check if data is found
        if not data:
            return "Unable to fetch available crypto tickers or no available crypto tickers found."
    
        # Extract the available crypto tickers
        tickers = data.get("tickers", [])
    
        # Stringify the available crypto tickers
        return json.dumps(tickers, indent=2)
  • Helper function used by the tool to make authenticated API requests to the Financial Datasets API.
    async def make_request(url: str) -> dict[str, any] | None:
        """Make a request to the Financial Datasets API with proper error handling."""
        # Load environment variables from .env file
        load_dotenv()
        
        headers = {}
        if api_key := os.environ.get("FINANCIAL_DATASETS_API_KEY"):
            headers["X-API-KEY"] = api_key
    
        async with httpx.AsyncClient() as client:
            try:
                response = await client.get(url, headers=headers, timeout=30.0)
                response.raise_for_status()
                return response.json()
            except Exception as e:
                return {"Error": str(e)}
  • server.py:225-225 (registration)
    The @mcp.tool() decorator registers the get_available_crypto_tickers function as an MCP tool.
    @mcp.tool()
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. It only states the action ('Gets') without details on permissions, rate limits, data freshness, or output format. This is insufficient for a tool with zero annotation coverage, lacking critical 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 a single, efficient sentence with no wasted words. It is appropriately sized and front-loaded, clearly stating the tool's purpose without redundancy or unnecessary detail.

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 and output schema, the description is incomplete. It does not explain what 'available crypto tickers' entails (e.g., list format, supported exchanges, update frequency), leaving gaps in understanding for the agent. This is inadequate for a tool with no structured support.

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%. The description does not add parameter information, which is unnecessary here. A baseline score of 4 is appropriate as no parameters exist to document.

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 states the tool's purpose ('Gets all available crypto tickers'), which is clear but vague. It specifies the verb ('Gets') and resource ('crypto tickers'), but lacks detail on scope or format, and does not differentiate from siblings like 'get_crypto_prices' or 'get_current_crypto_price'. This meets the minimum viable standard.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention context, prerequisites, or exclusions, such as how it differs from sibling tools that fetch specific crypto data. This leaves the agent without usage direction.

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

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/financial-datasets/mcp-server'

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