Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_stablecoin_charts_all

Retrieve historical market capitalization data for stablecoins to analyze trends and performance over time.

Instructions

GET /stablecoins/stablecoincharts/all

Get historical mcap sum of all stablecoins.

Parameters:
    stablecoin: stablecoin ID (optional)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stablecoinNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_stablecoin_charts_all' tool, decorated with @mcp.tool() for registration in FastMCP. It makes an API request to DefiLlama's stablecoin charts endpoint for all stablecoins, optionally filtered by stablecoin ID, and returns the JSON response as a string.
    @mcp.tool()
    async def get_stablecoin_charts_all(stablecoin: Optional[int] = None) -> str:
        """GET /stablecoins/stablecoincharts/all
        
        Get historical mcap sum of all stablecoins.
        
        Parameters:
            stablecoin: stablecoin ID (optional)
        """
        params = {}
        if stablecoin is not None:
            params['stablecoin'] = stablecoin
        result = await make_request('GET', '/stablecoins/stablecoincharts/all', params)
        return str(result)
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 is a GET request and describes the output ('historical mcap sum'), but lacks critical details like rate limits, authentication requirements, error handling, or pagination behavior. For a data-fetching tool with no annotations, 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.

Conciseness4/5

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

The description is concise and well-structured, with the endpoint path upfront followed by a clear purpose statement and parameter details. There's no wasted text, and information is presented in a logical order, making it easy to parse quickly.

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 that there's an output schema (which should cover return values), the description provides basic purpose and parameter info. However, for a tool with no annotations and incomplete parameter documentation, it lacks sufficient context on usage, behavior, and integration details. It's minimally adequate but has clear gaps in guidance and transparency.

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 some parameter semantics by noting that 'stablecoin' is an 'optional' 'stablecoin ID', which clarifies its purpose beyond the schema's generic 'Stablecoin' title. However, with 0% schema description coverage and only one parameter, it doesn't fully compensate—e.g., it doesn't explain what a 'stablecoin ID' is or provide examples. The baseline is adjusted due to low coverage but limited improvement.

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 sum of all stablecoins.' It specifies the verb ('Get') and resource ('historical mcap sum of all stablecoins'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_stablecoin_charts_by_chain' or 'get_stablecoin_history', which might have 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, context for usage, or comparisons to sibling tools such as 'get_stablecoin_charts_by_chain' or 'get_stablecoin_history'. This leaves the agent without clear direction on tool 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