Skip to main content
Glama
0xReisearch

REI Crypto MCP Server

by 0xReisearch

get_bridge_transactions

Retrieve bridge transaction data by specifying a bridge ID, date range, and optional filters like source chain or address to analyze cross-chain activity.

Instructions

GET /transactions/{id}

Get all transactions for a bridge within a date range.

Parameters:
    id: bridge ID (can be retrieved from /bridges)
    start_timestamp: start timestamp (Unix Timestamp) for date range
    end_timestamp: end timestamp (Unix Timestamp) for date range
    source_chain: filter by source chain (e.g., 'Polygon')
    address: filter by address in format {chain}:{address}
    limit: limit number of transactions returned (max 6000)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
start_timestampNo
end_timestampNo
source_chainNo
addressNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function for the 'get_bridge_transactions' tool. It constructs parameters based on inputs and makes an API request to DefiLlama's /transactions/{id} endpoint to retrieve bridge transactions.
    @mcp.tool()
    async def get_bridge_transactions(
        id: int,
        start_timestamp: Optional[int] = None,
        end_timestamp: Optional[int] = None,
        source_chain: Optional[str] = None,
        address: Optional[str] = None,
        limit: Optional[int] = None
    ) -> str:
        """GET /transactions/{id}
        
        Get all transactions for a bridge within a date range.
        
        Parameters:
            id: bridge ID (can be retrieved from /bridges)
            start_timestamp: start timestamp (Unix Timestamp) for date range
            end_timestamp: end timestamp (Unix Timestamp) for date range
            source_chain: filter by source chain (e.g., 'Polygon')
            address: filter by address in format {chain}:{address}
            limit: limit number of transactions returned (max 6000)
        """
        params = {}
        if start_timestamp is not None:
            params['starttimestamp'] = start_timestamp
        if end_timestamp is not None:
            params['endtimestamp'] = end_timestamp
        if source_chain is not None:
            params['sourcechain'] = source_chain
        if address is not None:
            params['address'] = address
        if limit is not None:
            params['limit'] = limit
        result = await make_request('GET', f'/transactions/{id}', 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 of behavioral disclosure. It mentions the 'limit' parameter has a maximum of 6000, which is useful context. However, it doesn't describe other important behavioral aspects like whether this is a read-only operation, potential rate limits, authentication requirements, pagination behavior, or error conditions. For a tool with 6 parameters and no annotations, this is a significant gap.

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 well-structured and appropriately sized. It starts with the HTTP method and endpoint, states the purpose clearly, then lists all parameters with helpful explanations. Every sentence earns its place, though it could be slightly more concise by combining some parameter explanations.

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 that there's an output schema (which handles return values) and the description provides good parameter semantics, the description is reasonably complete. However, for a tool with 6 parameters and no annotations, it should ideally include more behavioral context about how the tool actually works, error handling, and performance characteristics to be fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description provides excellent parameter semantics beyond the input schema. With 0% schema description coverage, the description fully compensates by explaining all 6 parameters: what 'id' represents and where to get it, that timestamps are Unix format, examples for 'source_chain' and 'address' formats, and the maximum value for 'limit'. This adds substantial value beyond the bare schema.

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: 'Get all transactions for a bridge within a date range.' This specifies the verb ('Get'), resource ('transactions'), and scope ('bridge within a date range'). However, it doesn't explicitly differentiate from sibling tools like 'get_bridge_day_stats' or 'get_bridge_volume', which might provide related but different data.

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 minimal usage guidance. It mentions that the 'id' parameter can be retrieved from '/bridges', but doesn't specify when to use this tool versus alternatives like 'get_bridge_day_stats' or 'get_bridge_volume'. No explicit when-not-to-use or prerequisite information is provided.

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