Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_stablecoin_dominance

Retrieve stablecoin dominance data for specific blockchain networks to analyze market share distribution and identify the largest stablecoin on each chain.

Instructions

GET /stablecoins/stablecoindominance/{chain}

Get stablecoin dominance per chain along with the info about the largest coin in a chain.

Parameters:
    chain: chain slug (e.g., 'Ethereum')
    stablecoin: stablecoin ID (optional)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYes
stablecoinNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • This is the handler function for the 'get_stablecoin_dominance' tool. It is decorated with @mcp.tool() which registers it in the MCP server and defines its schema from the signature and docstring. The function makes an API request to DefiLlama's stablecoin dominance endpoint.
    @mcp.tool()
    async def get_stablecoin_dominance(chain: str, stablecoin: Optional[int] = None) -> str:
        """GET /stablecoins/stablecoindominance/{chain}
        
        Get stablecoin dominance per chain along with the info about the largest coin in a chain.
        
        Parameters:
            chain: chain slug (e.g., 'Ethereum')
            stablecoin: stablecoin ID (optional)
        """
        params = {}
        if stablecoin is not None:
            params['stablecoin'] = stablecoin
        result = await make_request('GET', f'/stablecoins/stablecoindominance/{chain}', params)
        return str(result)
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 states it's a GET operation, implying read-only behavior, but lacks details on authentication needs, rate limits, error handling, or output format. The mention of 'largest coin in a chain' adds some context, but overall behavioral traits are insufficiently covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded, starting with the core purpose. It uses two sentences effectively, with no wasted words. However, the inclusion of 'GET /stablecoins/stablecoindominance/{chain}' is somewhat redundant with the tool name, slightly reducing efficiency.

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

Completeness3/5

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

Given 2 parameters with 0% schema coverage and an output schema present, the description provides basic purpose and parameter info but lacks usage guidelines and detailed behavioral context. It is minimally adequate for a read-only tool with output schema, but could be more complete by explaining when to use it and clarifying parameter details.

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?

Schema description coverage is 0%, so the description must compensate. It explains 'chain' as 'chain slug (e.g., 'Ethereum')' and 'stablecoin' as 'stablecoin ID (optional)', adding basic semantics. However, it does not clarify what 'stablecoin dominance' means or provide examples for 'stablecoin ID', leaving gaps in parameter understanding.

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: 'Get stablecoin dominance per chain along with the info about the largest coin in a chain.' It specifies the verb ('Get'), resource ('stablecoin dominance'), and scope ('per chain'), but does not explicitly differentiate from sibling tools like 'get_stablecoin_charts_by_chain' or 'get_stablecoins', which might offer overlapping functionality.

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 lists parameters but does not mention use cases, prerequisites, or comparisons to sibling tools such as 'get_stablecoin_charts_by_chain' or 'get_stablecoins', leaving the agent without context for selection.

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/0xReisearch/crypto-mcp-beta'

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