Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_bridges

Retrieve comprehensive bridge data with recent volume summaries to analyze cross-chain asset transfers in cryptocurrency ecosystems.

Instructions

GET /bridges

List all bridges along with summaries of recent bridge volumes.

Parameters:
    include_chains: set whether to include current previous day volume breakdown by chain

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_chainsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_bridges' tool, decorated with @mcp.tool() which handles both implementation and registration in MCP. It makes a GET request to the DefiLlama /bridges endpoint with optional chain inclusion parameter and returns the JSON response as string.
    @mcp.tool()
    async def get_bridges(include_chains: bool = True) -> str:
        """GET /bridges
        
        List all bridges along with summaries of recent bridge volumes.
        
        Parameters:
            include_chains: set whether to include current previous day volume breakdown by chain
        """
        params = {'includeChains': str(include_chains).lower()}
        result = await make_request('GET', '/bridges', params)
        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 the full burden. It mentions 'List all bridges' but doesn't disclose behavioral traits such as pagination, rate limits, authentication needs, or what 'recent' means temporally. The description is minimal and lacks crucial operational details for a read operation.

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 appropriately sized and front-loaded, starting with the core purpose followed by parameter details. Every sentence adds value without redundancy. However, it could be slightly more structured by separating the purpose and parameters more clearly.

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's simplicity (1 parameter, no annotations, but with an output schema), the description is moderately complete. It covers the purpose and parameter semantics adequately, but lacks behavioral transparency and usage guidelines. The output schema likely handles return values, so the description doesn't need to explain those.

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 description adds meaningful context for the single parameter 'include_chains', explaining it as 'set whether to include current previous day volume breakdown by chain'. This clarifies the parameter's purpose beyond the schema's basic title and type, compensating for the 0% schema description coverage. No other parameters exist, so this is sufficient.

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: 'List all bridges along with summaries of recent bridge volumes.' It specifies the verb ('List'), resource ('bridges'), and scope ('summaries of recent bridge volumes'), which distinguishes it from siblings like 'get_bridge_details' or 'get_bridge_transactions'. However, it doesn't explicitly differentiate from 'get_bridge_volume', which might overlap in functionality.

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 siblings like 'get_bridge_details' for detailed info or 'get_bridge_volume' for volume-specific data, nor does it specify prerequisites or exclusions. Usage is implied by the purpose but lacks explicit 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