Skip to main content
Glama
kukapay

crypto-stocks-mcp

get_stock_list

Retrieve a formatted list of crypto-related stocks with ticker symbols and company names for investment analysis.

Instructions

Return a list of available crypto-related stocks in a table format.

Returns:
    str: An ASCII table string containing the ticker and name of crypto-related stocks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:31-47 (handler)
    The main handler function for the 'get_stock_list' tool. It is registered via the @mcp.tool() decorator and generates a tabulated list of available crypto-related stocks using the CRYPTO_STOCKS dictionary and the tabulate library.
    @mcp.tool()
    def get_stock_list() -> str:
        """Return a list of available crypto-related stocks in a table format.
    
        Returns:
            str: An ASCII table string containing the ticker and name of crypto-related stocks.
        """
        table_data = [
            [ticker, name]
            for ticker, name in CRYPTO_STOCKS.items()
        ]
        return tabulate(
            table_data,
            headers=["Ticker", "Name"],
            tablefmt="grid",
            stralign="left"
        )
  • main.py:10-27 (helper)
    Constant dictionary defining the list of crypto-related stock tickers and their full names, used by the get_stock_list handler.
    CRYPTO_STOCKS = {
      "BMNR": "BitMine Immersion Technologies, Inc.",
      "CRCL": "Circle Internet Group Inc.",
      "SBET": "SharpLink Gaming Inc.",  
      "SRM": "Tron Inc.",
      "DFDV": "DeFi Development Corp.",
      "MSTR": "MicroStrategy Incorporated",
      "COIN": "Coinbase Global Inc.",
      "MARA": "Marathon Digital Holdings",
      "RIOT": "Riot Platforms Inc.",
      "HIVE": "HIVE Digital Technologies",
      "CORZ": "Core Scientific Inc.",
      "IREN": "Iris Energy Limited",
      "CLSK": "CleanSpark Inc.",
      "HUT": "Hut 8 Corp",
      "CIFR": "Cipher Mining Inc.",
      "BITF": "Bitfarms Ltd"
    }
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 the tool returns a list in an ASCII table format, which is useful, but lacks details on potential behaviors like rate limits, data freshness, error handling, or authentication needs. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it operates.

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 highly concise and well-structured: two brief sentences that directly state the tool's purpose and output format without any wasted words. It's front-loaded with the main action and efficiently conveys essential information.

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

Completeness4/5

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

Given the tool's low complexity (0 parameters, simple output) and the presence of an output schema (which handles return value documentation), the description is reasonably complete. It covers the purpose and output format, though it could benefit from more behavioral context or usage guidelines to fully guide an agent.

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 input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description doesn't add parameter details, but since there are no parameters, this is acceptable. The baseline for 0 parameters is 4, as the description needn't compensate for missing param info.

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 tool's purpose: 'Return a list of available crypto-related stocks in a table format.' It specifies the verb ('return'), resource ('crypto-related stocks'), and output format ('table format'), which is specific and actionable. However, it doesn't explicitly differentiate from sibling tools like 'get_historical_prices' or 'get_stock_price', which focus on price data rather than listing stocks.

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 sibling tools or contexts where this tool is preferred, such as for initial discovery of crypto stocks before fetching prices. Without any usage context or exclusions, the agent must infer usage based on 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

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/kukapay/crypto-stocks-mcp'

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