Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_forks

Retrieve comprehensive data on all blockchain forks across protocols using the REI Crypto MCP Server's integrated API access.

Instructions

GET /api/forks

Overview of all forks 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_forks' tool. It is decorated with @mcp.tool() which registers it in the FastMCP server. The function makes a GET request to the DefiLlama API endpoint '/api/forks' using the shared make_request helper and returns the result as a string.
    @mcp.tool()
    async def get_forks() -> str:
        """GET /api/forks
        
        Overview of all forks across all protocols.
        """
        result = await make_request('GET', '/api/forks')
        return str(result)
  • Shared helper function used by get_forks (and all 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)}"
  • The @mcp.tool() decorator registers the get_forks function as a tool in the FastMCP server.
    @mcp.tool()
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'GET' and 'Overview', implying a read-only operation, but lacks details on rate limits, authentication needs, response format, pagination, or error handling. This is inadequate for a tool with no annotation coverage, as it leaves critical behavioral traits unspecified.

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 brief and front-loaded with the API endpoint and purpose in two sentences, with no wasted words. However, the second sentence 'Overview of all forks across all protocols.' could be more precise (e.g., specifying what data is included in the overview), 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 the tool has 0 parameters, 100% schema coverage, and an output schema exists, the description's minimal content is somewhat acceptable. However, with no annotations and many sibling tools, it lacks sufficient context on behavior, usage, and differentiation, making it incomplete for effective agent operation without additional inference.

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 information is needed in the description. The description does not add any parameter semantics, but this is acceptable given the absence of parameters, warranting a baseline score of 4 as it does not detract from usability.

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 an 'Overview of all forks across all protocols' with the verb 'GET' and resource '/api/forks', making the purpose specific and understandable. However, it does not explicitly differentiate this tool from its many sibling tools (e.g., get_protocols, get_protocol_details) beyond the focus on 'forks', leaving some ambiguity about its unique scope.

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. With numerous sibling tools like get_protocols or get_protocol_details, there is no indication of context, prerequisites, or exclusions, leaving the agent to infer usage based solely on the tool name and minimal description.

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