Skip to main content
Glama
ymylive
by ymylive

get_companies_holdings

Retrieve public companies' Bitcoin or Ethereum treasury holdings, including total holdings, value, and market cap dominance. Ideal for tracking institutional adoption and answering queries about corporate crypto treasuries.

Instructions

Get public companies' BTC or ETH treasury holdings.

Useful for "which companies own BTC?" or "what's MicroStrategy's stack?" style questions, and for tracking institutional adoption.

Args: coin_id: Either "bitcoin" or "ethereum" — those are the only assets CoinGecko tracks for public-treasury data.

Returns: Object with total_holdings, total_value_usd, market_cap_dominance, and companies — an array of { name, symbol, country, total_holdings, total_entry_value_usd, total_current_value_usd, percentage_of_total_supply }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coin_idNobitcoin

Implementation Reference

  • The actual tool handler. Decorated with @mcp.tool(), accepts a Literal['bitcoin','ethereum'] coin_id (default 'bitcoin'), makes a GET request to CoinGecko's /companies/public_treasury/{coin_id} endpoint via the shared _cg_get helper, and returns raw JSON.
    @mcp.tool()
    async def get_companies_holdings(
        coin_id: Literal["bitcoin", "ethereum"] = "bitcoin",
    ) -> Any:
        """Get public companies' BTC or ETH treasury holdings.
    
        Useful for "which companies own BTC?" or "what's MicroStrategy's stack?"
        style questions, and for tracking institutional adoption.
    
        Args:
            coin_id: Either "bitcoin" or "ethereum" — those are the only assets
                CoinGecko tracks for public-treasury data.
    
        Returns:
            Object with `total_holdings`, `total_value_usd`, `market_cap_dominance`,
            and `companies` — an array of `{ name, symbol, country, total_holdings,
            total_entry_value_usd, total_current_value_usd, percentage_of_total_supply }`.
        """
        return await _cg_get(f"/companies/public_treasury/{coin_id}")
  • Input schema: coin_id is Literal['bitcoin','ethereum'] with default 'bitcoin'. Output described in docstring: object with total_holdings, total_value_usd, market_cap_dominance, and companies array.
    Args:
        coin_id: Either "bitcoin" or "ethereum" — those are the only assets
            CoinGecko tracks for public-treasury data.
    
    Returns:
        Object with `total_holdings`, `total_value_usd`, `market_cap_dominance`,
        and `companies` — an array of `{ name, symbol, country, total_holdings,
        total_entry_value_usd, total_current_value_usd, percentage_of_total_supply }`.
    """
  • Tool registration via @mcp.tool() decorator. The 'mcp' object is the FastMCP instance imported from coin_mcp.core (line 7).
    @mcp.tool()
  • _cg_get helper — constructs the full URL using _coingecko_base() and passes auth headers, then delegates to _http_get which uses the TTL cache.
    async def _cg_get(path: str, params: dict[str, Any] | None = None) -> Any:
        return await _http_get(
            f"{_coingecko_base()}{path}",
            params=params,
            headers=_coingecko_headers(),
        )
Behavior4/5

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

Without annotations, the description fully outlines return structure (total_holdings, total_value_usd, market_cap_dominance, companies array with fields), and notes limitation to Bitcoin and Ethereum. No behavioral contradictions.

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?

Description is brief, front-loaded with purpose, and every sentence (including Args/Returns) provides essential information without redundancy or filler.

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

Completeness5/5

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

Given the single parameter with enum and no output schema, the description fully covers usage, parameter, and return structure, leaving no gaps for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

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

Despite 0% schema coverage, the Args section explains coin_id's allowed values (bitcoin/ethereum) and the reasoning (only assets tracked), adding meaning beyond the enum and default in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool retrieves public companies' BTC/ETH treasury holdings with specific examples ('which companies own BTC?', 'MicroStrategy stack'), and differentiates from siblings which cover prices, markets, exchanges, etc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides concrete use cases (tracking institutional adoption) and implies applicability to Bitcoin/Ethereum treasury queries. No explicit when-not or alternatives given, but the examples make usage clear.

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/ymylive/coin-mcp'

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