Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_stablecoin_prices

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

Instructions

GET /stablecoins/stablecoinprices

Get historical prices of all stablecoins.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function decorated with @mcp.tool() that implements the get_stablecoin_prices tool. It fetches historical prices of all stablecoins from the DefiLlama API endpoint '/stablecoins/stablecoinprices' using the shared make_request helper and returns the JSON result as a string.
    @mcp.tool()
    async def get_stablecoin_prices() -> str:
        """GET /stablecoins/stablecoinprices
        
        Get historical prices of all stablecoins.
        """
        result = await make_request('GET', '/stablecoins/stablecoinprices')
        return str(result)
  • The @mcp.tool() decorator registers the get_stablecoin_prices function as an MCP tool.
    @mcp.tool()
  • Shared helper function used by get_stablecoin_prices and other tools 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. It states the tool retrieves historical prices but doesn't disclose behavioral traits such as rate limits, authentication requirements, data freshness, pagination, error handling, or response format. This is a significant gap for a tool with no annotation coverage.

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/stablecoinprices') is redundant API endpoint information that doesn't add value for an AI agent. The second sentence is clear but could be more front-loaded with essential context.

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, 100% schema coverage, and an output schema exists, the description is minimally adequate. However, with no annotations and siblings offering similar functionality, it lacks completeness in distinguishing use cases and behavioral context, which could confuse an agent.

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%. The description doesn't need to add parameter semantics, as there are none to document. It appropriately focuses on the tool's purpose without unnecessary parameter details.

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 prices of all stablecoins.' It specifies the verb ('Get'), resource ('historical prices'), and scope ('all stablecoins'). However, it doesn't differentiate from sibling tools like 'get_stablecoin_history' or 'get_current_prices', which might offer similar data with different timeframes or scopes.

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 siblings like 'get_stablecoin_history' and 'get_current_prices' available, there's no indication of whether this tool is for bulk historical data, real-time prices, or specific time ranges. Usage context is implied but not explicit.

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