Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_protocols

Retrieve a list of all DeFi protocols with their total value locked (TVL) from DefiLlama to analyze market positions and trends.

Instructions

GET /api/protocols

List all protocols on defillama along with their tvl.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_protocols' MCP tool. It fetches the list of all protocols and their TVL from the DefiLlama API using the shared make_request utility.
    async def get_protocols() -> str:
        """GET /api/protocols
        
        List all protocols on defillama along with their tvl.
        """
        result = await make_request('GET', '/api/protocols')
        return str(result)
  • The @mcp.tool() decorator registers the get_protocols function as an available tool in the FastMCP server.
    @mcp.tool()
  • Shared helper function used by get_protocols (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)}"
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool lists protocols with TVL but doesn't cover critical aspects like whether it's a read-only operation, potential rate limits, authentication needs, pagination behavior, or data freshness. This leaves significant gaps for a tool that likely fetches financial data.

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 efficiently structured in two sentences: the first provides the API endpoint, and the second explains the functionality. There's no wasted text, though it could be slightly more polished by combining the sentences for better flow.

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 an output schema (which handles return values) and 0 parameters with full schema coverage, the description's main job is purpose clarification. It does this adequately but lacks behavioral context (especially important with no annotations) and usage guidance relative to siblings, making it minimally complete but with clear gaps.

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 input requirements. The description appropriately doesn't add parameter information, maintaining focus on the tool's purpose. A baseline of 4 is appropriate for zero-parameter 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 ('List') and resource ('protocols on defillama'), and includes the additional output detail ('along with their tvl'). However, it doesn't explicitly differentiate from sibling tools like 'get_protocol_details' or 'get_protocol_tvl', which prevents a perfect score.

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 sibling tools like 'get_protocol_details' for specific protocol information or 'get_protocol_tvl' for TVL-focused queries, leaving the agent without usage context.

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