Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_stablecoin_chains

Retrieve the total market capitalization of stablecoins across different blockchain networks to analyze asset distribution and liquidity.

Instructions

GET /stablecoins/stablecoinchains

Get current mcap sum of all stablecoins on each chain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function decorated with @mcp.tool(), which registers the tool and defines its execution logic. It fetches stablecoin chains data from DefiLlama API endpoint '/stablecoins/stablecoinchains' using the shared make_request helper.
    @mcp.tool()
    async def get_stablecoin_chains() -> str:
        """GET /stablecoins/stablecoinchains
        
        Get current mcap sum of all stablecoins on each chain.
        """
        result = await make_request('GET', '/stablecoins/stablecoinchains')
        return str(result)
  • The @mcp.tool() decorator registers the get_stablecoin_chains function as an MCP tool.
    @mcp.tool()
  • Shared helper function used by get_stablecoin_chains to make HTTP requests to the DefiLlama API.
    async def make_request(method: str, endpoint: str, params: Optional[Dict[str, Any]] = None) -> Any:
        """Make a request to the DefiLlama API."""
        try:
            response = await client.request(method, endpoint, params=params)
            response.raise_for_status()
            return response.json()
        except Exception as e:
            return f"Error: {str(e)}"
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 retrieves data ('Get'), implying a read-only operation, but doesn't mention any behavioral traits such as rate limits, authentication needs, data freshness, or error handling. For a tool with zero annotation coverage, this is a significant gap in transparency.

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

Conciseness3/5

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

The description is concise with two sentences, but the first sentence ('GET /stablecoins/stablecoinchains') is redundant API endpoint information that doesn't add value for an AI agent. The second sentence is the core description. While efficient, the inclusion of the endpoint reduces clarity and front-loading effectiveness.

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 the tool has 0 parameters, an output schema exists, and no annotations, the description is minimally adequate. It states what the tool does but lacks context on usage, behavioral details, or output interpretation. The presence of an output schema means return values are documented elsewhere, but the description doesn't fully compensate for the missing behavioral transparency.

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% (though empty). The description doesn't need to explain parameters, and it doesn't add or contradict any parameter information. A baseline of 4 is appropriate for a parameterless tool where the schema fully covers the absence of inputs.

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 current mcap sum of all stablecoins on each chain.' It specifies the verb ('Get'), resource ('mcap sum of all stablecoins'), and scope ('on each chain'). However, it doesn't explicitly differentiate from sibling tools like 'get_stablecoins' or 'get_stablecoin_charts_by_chain', which prevents a perfect score.

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 many sibling tools related to stablecoins (e.g., 'get_stablecoins', 'get_stablecoin_charts_by_chain'), there is no indication of context, prerequisites, or exclusions. The agent must infer usage based on the purpose 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/0xReisearch/crypto-mcp-beta'

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