Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_etf_overview_eth

Retrieve overview data for Ethereum ETFs using the REI Crypto MCP Server to access cryptocurrency information without managing API keys.

Instructions

GET /etfs/overviewEth

Get ETH ETFs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'get_etf_overview_eth' tool, decorated with @mcp.tool() for registration in FastMCP. It fetches ETH ETF overview data from the DefiLlama API endpoint '/etfs/overviewEth' and returns the JSON response as a string.
    @mcp.tool()
    async def get_etf_overview_eth() -> str:
        """GET /etfs/overviewEth
        
        Get ETH ETFs.
        """
        result = await make_request('GET', '/etfs/overviewEth')
        return str(result)
  • The @mcp.tool() decorator registers the get_etf_overview_eth function as an MCP tool.
    @mcp.tool()
  • Shared helper function used by get_etf_overview_eth 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 full burden. It only states it's a GET operation, lacking details on rate limits, authentication needs, response format, or error handling. This leaves significant behavioral gaps for an agent.

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?

It's brief but inefficiently structured with redundant URL-like text ('GET /etfs/overviewEth'). The core description 'Get ETH ETFs' is clear but could be more front-loaded without the extra line.

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 0 parameters, 100% schema coverage, and an output schema exists, the description minimally covers purpose. However, without annotations and with sibling tools present, it lacks sufficient context on usage and behavior, making it incomplete for optimal agent guidance.

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?

With 0 parameters and 100% schema coverage, the input schema fully documents no inputs. The description doesn't add parameter info, which is acceptable here as there are no parameters to explain, aligning with the baseline for zero parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Get ETH ETFs' which provides a basic verb+resource combination, but it's vague about what specific data is retrieved (e.g., overview, list, metrics). It doesn't distinguish from sibling 'get_etf_overview' which likely provides general ETF data, leaving ambiguity about the ETH-specific scope.

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 on when to use this tool versus alternatives like 'get_etf_overview' or 'get_etf_history_eth'. The description merely restates the action without context about appropriate scenarios or exclusions.

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