Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_stablecoin_history

Retrieve historical market capitalization and blockchain distribution data for any stablecoin to analyze trends and track performance over time.

Instructions

GET /stablecoins/stablecoin/{asset}

Get historical mcap and historical chain distribution of a stablecoin.

Parameters:
    asset: stablecoin ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'get_stablecoin_history' tool, registered via @mcp.tool(). It makes an API request to DefiLlama's /stablecoins/stablecoin/{asset} endpoint to retrieve historical market cap and chain distribution data for the specified stablecoin asset ID.
    @mcp.tool()
    async def get_stablecoin_history(asset: int) -> str:
        """GET /stablecoins/stablecoin/{asset}
        
        Get historical mcap and historical chain distribution of a stablecoin.
        
        Parameters:
            asset: stablecoin ID
        """
        result = await make_request('GET', f'/stablecoins/stablecoin/{asset}')
        return str(result)
  • Shared helper function used by get_stablecoin_history (and other tools) to perform HTTP requests to the DefiLlama API using the configured httpx client.
    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 it's a GET operation (implying read-only) and mentions retrieving historical data, but lacks details on authentication needs, rate limits, error handling, data freshness, or output format. For a tool with no annotations, this leaves significant gaps in understanding its behavior and constraints.

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 HTTP method and endpoint, followed by the core purpose and a parameter list. It avoids unnecessary fluff, with every sentence contributing directly to the tool's definition. However, the structure could be slightly improved by integrating the parameter explanation more seamlessly, but it remains efficient overall.

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's moderate complexity (historical data retrieval), no annotations, and an output schema present, the description is partially complete. It covers the basic purpose and parameter, but lacks behavioral context (e.g., data scope, limitations) that annotations would typically provide. The output schema mitigates the need to explain return values, but overall, the description feels minimal for a tool with potential nuances in historical data access.

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?

The description adds minimal semantics: it lists 'asset: stablecoin ID' as a parameter, which matches the input schema's single required parameter 'asset' of type integer. However, schema description coverage is 0%, so the schema provides no additional details. The description doesn't clarify what a 'stablecoin ID' entails (e.g., numeric codes, naming conventions), offering only basic context without compensating for the low schema coverage.

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 historical mcap and historical chain distribution of a stablecoin.' It specifies the verb ('Get') and resource ('historical mcap and historical chain distribution'), making it distinct from sibling tools like 'get_stablecoins' (list) or 'get_stablecoin_prices' (current prices). However, it doesn't explicitly differentiate from 'get_stablecoin_charts_all' or 'get_stablecoin_charts_by_chain', which might also involve historical data, leaving some ambiguity.

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 like 'get_stablecoin_charts_all' or 'get_stablecoin_charts_by_chain', which could be related for historical data, nor does it specify prerequisites or exclusions (e.g., asset ID format, time ranges). Usage is implied only by the tool name and description, with no explicit 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