Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_categories

Retrieve all cryptocurrency protocol categories from DeFiLlama Pro to analyze market segments and track sector performance.

Instructions

GET /api/categories

Overview of all categories across all protocols.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_categories' tool. It is decorated with @mcp.tool(), which registers it with the MCP server. The function makes an API request to DefiLlama's /api/categories endpoint and returns the result as a string.
    @mcp.tool()
    async def get_categories() -> str:
        """GET /api/categories
        
        Overview of all categories across all protocols.
        """
        result = await make_request('GET', '/api/categories')
        return str(result)
  • Shared helper function used by get_categories (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 states this is a GET operation (implying read-only) and mentions 'overview' but doesn't describe 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 /api/categories' could be inferred from the tool name. The second sentence provides the core value. While concise, the structure could be more front-loaded with the essential purpose rather than leading with implementation details.

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, for a data retrieval tool with no annotations, it should ideally describe what 'categories' means in this context, the response structure, or any limitations. The existence of an output schema reduces but doesn't eliminate the need for contextual explanation.

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 already fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist, which is correct. Baseline for 0 parameters is 4.

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 as 'Overview of all categories across all protocols' which is a specific verb+resource combination. It distinguishes itself from siblings by focusing on categories rather than users, prices, bridges, or other data types. However, it doesn't explicitly contrast with potential similar tools (though none appear in the sibling 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 prerequisites, timing considerations, or how it differs from other data retrieval tools in the sibling list. The agent must infer usage from the title and description alone.

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