Skip to main content
Glama
deenesjakoruzh
0xReisearch

REI Crypto MCP Server

by 0xReisearch
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_etf_history_eth

Retrieve historical assets under management (AUM) data for all Ethereum ETFs to analyze performance trends and investment patterns over time.

Instructions

GET /etfs/historyEth

Historical AUM of all ETH ETFs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • defillama_server.py:419-426 (handler)
    The handler function for the 'get_etf_history_eth' tool. It is registered via the @mcp.tool() decorator and fetches historical AUM data for ETH ETFs from the DefiLlama API endpoint '/etfs/historyEth' using the shared make_request helper.
    @mcp.tool()
async def get_etf_history_eth() -> str:
    """GET /etfs/historyEth
    
    Historical AUM of all ETH ETFs.
    """
    result = await make_request('GET', '/etfs/historyEth')
    return str(result)

Tool Definition Quality

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions 'Historical AUM' but doesn't specify time ranges, data granularity, authentication needs, rate limits, or response format. The HTTP method 'GET' implies read-only, but this isn't explicitly stated.

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

Conciseness5/5

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

Extremely concise with three short lines: endpoint, purpose, and scope. Every sentence is essential, front-loading the key information without any wasted words or redundancy.

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 and an output schema exists, the description is minimally adequate. However, for a data retrieval tool with no annotations, it lacks context on data format, time periods, or usage constraints, leaving gaps in understanding how to interpret results.

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 with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate given the empty schema, earning a baseline score above minimum viable.

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 retrieves historical AUM (Assets Under Management) data for ETH ETFs, with a specific verb ('GET') and resource ('/etfs/historyEth'). It distinguishes from sibling 'get_etf_history' by specifying 'Eth' scope, though not explicitly contrasting them.

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_history' or 'get_etf_overview_eth' is provided. The description only states what it does, not when it's appropriate or what distinguishes it from similar tools.

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