Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_user_data

Retrieve user data for specific protocols from crypto analytics platforms, enabling analysis of metrics like active users without managing API keys.

Instructions

GET /api/userData/{type}/{protocolId}

Get user data by type and protocol.

Parameters:
    type: data type (e.g., 'activeUsers')
    protocol_id: protocol ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes
protocol_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_user_data' MCP tool. It is registered via the @mcp.tool() decorator and implements the logic to fetch user data from the DefiLlama API endpoint /api/userData/{type}/{protocol_id} using the shared make_request helper.
    @mcp.tool()
    async def get_user_data(type: str, protocol_id: int) -> str:
        """GET /api/userData/{type}/{protocolId}
        
        Get user data by type and protocol.
        
        Parameters:
            type: data type (e.g., 'activeUsers')
            protocol_id: protocol ID
        """
        result = await make_request('GET', f'/api/userData/{type}/{protocol_id}')
        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 full burden. It mentions it's a GET operation but doesn't disclose behavioral traits like authentication needs, rate limits, error handling, or what the output contains. The description is minimal and lacks critical operational context.

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 with the core purpose, followed by parameter details. It avoids unnecessary verbosity, though the structure could be improved by integrating the HTTP endpoint more naturally into the description.

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 2 parameters with 0% schema coverage and an output schema present, the description is incomplete. It lacks details on parameter semantics and behavioral context, but the output schema mitigates some gaps by presumably defining return values. This results in a minimally adequate but insufficient description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It lists parameters with brief examples ('e.g., 'activeUsers'') but doesn't explain valid values, constraints, or the relationship between type and protocol_id. This adds minimal meaning beyond the bare schema.

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 user data by type and protocol' which provides a basic purpose, but it's vague about what 'user data' entails and doesn't distinguish from sibling tools like 'get_active_users'. The HTTP method 'GET' is mentioned but doesn't clarify the action beyond retrieving data.

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 is provided on when to use this tool versus alternatives. With siblings like 'get_active_users' that might overlap, the description offers no context on differentiation, prerequisites, or appropriate use cases.

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