Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_entities

Retrieve a list of all cryptocurrency entities from integrated DeFi and crypto data sources to analyze market participants and track ecosystem growth.

Instructions

GET /api/entities

List all entities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'get_entities' tool, registered with @mcp.tool(). It makes a GET request to the DefiLlama API endpoint '/api/entities' using the shared make_request helper and returns the JSON response as a string.
    @mcp.tool()
    async def get_entities() -> str:
        """GET /api/entities
        
        List all entities.
        """
        result = await make_request('GET', '/api/entities')
        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 'GET /api/entities' which implies a read-only HTTP operation, but doesn't disclose behavioral traits like pagination, rate limits, authentication needs, or what 'entities' encompasses. The description is minimal and lacks crucial 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 very concise with two short lines, front-loading the purpose. However, it includes the endpoint path 'GET /api/entities' which might be redundant if the tool name already implies this, slightly reducing efficiency.

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 and an output schema exists, the description doesn't need to explain return values. However, with no annotations and a generic purpose among many siblings, it lacks context on what 'entities' are and operational behavior, making it incomplete for effective use.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here, earning a baseline score of 4 for zero-parameter tools.

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 the tool 'List all entities' which provides a clear verb+resource combination, but it doesn't differentiate from sibling tools like 'get_protocols' or 'get_categories' that might also list different types of entities. The purpose is understandable but generic.

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 many sibling tools that fetch different data types (e.g., get_protocols, get_stablecoins), the description lacks context on what 'entities' refers to or when this is the appropriate choice.

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