Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_chain_assets

Retrieve comprehensive asset data across multiple blockchain networks using aggregated crypto APIs to analyze cross-chain holdings and market positions.

Instructions

GET /api/chainAssets

Get assets of all chains.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'get_chain_assets' tool. It is decorated with @mcp.tool() which also serves as registration. The function makes an asynchronous HTTP GET request to the DefiLlama API endpoint '/api/chainAssets' using the shared make_request helper and returns the JSON result as a string.
    @mcp.tool()
    async def get_chain_assets() -> str:
        """GET /api/chainAssets
        
        Get assets of all chains.
        """
        result = await make_request('GET', '/api/chainAssets')
        return str(result)
  • Shared helper function used by get_chain_assets 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_chain_assets function as an MCP tool.
    @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. It states it's a GET operation, implying read-only behavior, but lacks details on permissions, rate limits, pagination, or response format. For a tool with no annotations, this is a significant gap in behavioral disclosure.

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 and front-loaded with the core purpose, but includes redundant information (the API endpoint 'GET /api/chainAssets') that doesn't add value for an AI agent. It could be more streamlined by focusing solely on the functional intent.

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 no annotations, 0 parameters, and an output schema exists, the description is minimally adequate. It states the purpose but lacks behavioral context (e.g., what 'assets' entail, data freshness). The output schema likely covers return values, so completeness is borderline but has 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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, which is acceptable here. Baseline is 4 for zero parameters, as it doesn't need to compensate for any gaps.

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 verb ('Get') and resource ('assets of all chains'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_chains' or 'get_historical_chain_tvl', which might also relate to chain data, so it doesn't reach the highest 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. With many sibling tools related to chains and assets (e.g., 'get_chains', 'get_historical_chain_tvl'), there's no indication of context, prerequisites, or exclusions, leaving usage ambiguous.

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