Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_active_users

Retrieve active user data for blockchain chains and protocols to monitor engagement and usage metrics.

Instructions

GET /api/activeUsers

Get active users on our chains and protocols pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'get_active_users' tool. It makes a GET request to the DefiLlama API endpoint '/api/activeUsers' using the shared make_request helper and returns the result as a string. The @mcp.tool() decorator registers it as an MCP tool.
    @mcp.tool()
    async def get_active_users() -> str:
        """GET /api/activeUsers
        
        Get active users on our chains and protocols pages.
        """
        result = await make_request('GET', '/api/activeUsers')
        return str(result)
  • The @mcp.tool() decorator registers the get_active_users function as an MCP tool.
    @mcp.tool()
  • Shared helper function used by get_active_users (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?

With no annotations provided, the description carries full burden for behavioral disclosure. It only states what data is retrieved ('active users') without mentioning response format, pagination, rate limits, authentication requirements, or error conditions. For a data retrieval tool with zero annotation coverage, this leaves significant behavioral gaps.

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 brief (two sentences) but includes redundant information - the HTTP method 'GET' is already implied by the tool name starting with 'get_'. The second sentence is useful but could be more efficiently integrated. The structure is front-loaded with the API endpoint, which is less helpful than starting with the tool's purpose.

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 no parameters, an output schema exists, and it's a simple data retrieval operation, the description is minimally adequate. However, with no annotations and a generic 'active users' concept, more context about what constitutes 'active' or the data format would be helpful. The existence of an output schema reduces but doesn't eliminate the need for some behavioral context.

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 the schema fully documents the absence of parameters. The description doesn't need to add parameter information, and it appropriately doesn't mention any parameters. This meets the baseline expectation for parameterless tools.

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 with a specific verb ('Get') and resource ('active users'), and specifies the scope ('on our chains and protocols pages'). It doesn't explicitly differentiate from sibling tools, but the specificity of 'active users' makes its purpose distinct from other data retrieval tools in the list.

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, exclusions, or comparison with sibling tools like 'get_user_data' or 'get_protocols' that might overlap in user-related data retrieval.

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