Skip to main content
Glama
kukapay

ethereum-validator-queue-mcp

get_exit_queue

Retrieve current Ethereum validator exit queue statistics including queue length, active validators, total exiting balance, and estimated wait time to monitor staking dynamics.

Instructions

Get current Ethereum validator exit queue statistics.

Returns:
    A string containing:
    - Current exit queue length (number of validators waiting to exit)
    - Total active validators
    - Total balance of exiting validators in ETH
    - Estimated wait time (based on ~900 exits per day)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:40-67 (handler)
    The handler function for the 'get_exit_queue' tool. It fetches Ethereum validator exit queue statistics from the beaconcha.in API, including queue length, active validators, exiting balance, and estimated wait time. Decorated with @mcp.tool() for registration.
    @mcp.tool()
    async def get_exit_queue() -> str:
        """Get current Ethereum validator exit queue statistics.
        
        Returns:
            A string containing:
            - Current exit queue length (number of validators waiting to exit)
            - Total active validators
            - Total balance of exiting validators in ETH
            - Estimated wait time (based on ~900 exits per day)
        """
        async with httpx.AsyncClient() as client:
            try:
                response = await client.get("https://beaconcha.in/api/v1/validators/queue")
                response.raise_for_status()
                data = response.json()["data"]
                exiting = data.get("beaconchain_exiting", 0)
                validators_count = data.get("validatorscount", 0)
                exiting_balance = data.get("beaconchain_exiting_balance", 0) / 1e9 if data.get("beaconchain_exiting_balance") else 0
                return (
                    f"Current exit queue length: {exiting} validators\n"
                    f"Total active validators: {validators_count}\n"
                    f"Exiting validators balance: {exiting_balance:.2f} ETH\n"
                    f"Estimated wait time: Approximately {exiting / 900:.1f} days "
                    f"(assuming ~900 exits per day)"
                )
            except Exception as e:
                return f"Error fetching exit queue data: {str(e)}"
Behavior3/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 discloses that the tool returns statistics (a read operation) and includes estimated wait time based on a daily exit rate, which adds useful context. However, it lacks details on permissions, rate limits, or error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the purpose, followed by a bulleted list of return values. Every sentence earns its place, with no wasted words, making it efficient and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no annotations, but with an output schema), the description is complete enough. It explains the purpose and details the return values, though it could benefit from usage guidance relative to sibling tools to fully cover context.

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?

There are 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately focuses on the return values without redundant parameter information, meeting the baseline for tools with no parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Get current Ethereum validator exit queue statistics') and distinguishes it from sibling tools like 'get_activation_queue' and 'get_validator_status' by focusing on exit queue data rather than activation or individual validator status.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_activation_queue' or 'get_validator_status'. The description only states what it returns, not the context or scenarios where it should be preferred over sibling tools.

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/kukapay/ethereum-validator-queue-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server