Skip to main content
Glama
tywenk

Model Context Protocol Server for Solana Client

by tywenk

validator_exit

Initiate a validator exit request on the Solana blockchain using the Model Context Protocol Server. This tool facilitates the process of requesting a validator to exit, ensuring proper blockchain node management.

Instructions

Request to have the validator exit.

Returns: str: Validator exit request result

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function decorated with @mcp.tool(), which registers and implements the 'validator_exit' MCP tool. It uses an AsyncClient to call validator_exit on the RPC endpoint and returns a formatted result string.
    @mcp.tool()
    async def validator_exit() -> str:
        """Request to have the validator exit.
    
        Returns:
            str: Validator exit request result
        """
        async with AsyncClient(rpc_url) as client:
            result = await client.validator_exit()
            return f"Validator exit request: {result}"
Behavior2/5

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

With no annotations provided, the description carries full burden. It mentions the action ('Request to have the validator exit') but doesn't disclose critical behavioral traits: whether this is a destructive operation, requires specific permissions, has irreversible consequences, or involves network changes. The return value description ('Validator exit request result') is vague.

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 brief and front-loaded with the core purpose in the first sentence. The second sentence about returns is somewhat redundant but not wasteful. Overall, it's efficiently structured with minimal fluff.

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

Completeness2/5

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

Given the tool's complexity (likely a significant network operation), lack of annotations, no output schema, and vague return description, the description is incomplete. It doesn't explain what 'validator exit' entails, success/failure conditions, or system impacts, leaving critical context gaps for an AI agent.

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 no parameter documentation is needed. The description appropriately doesn't discuss parameters, which aligns with the schema. Baseline is 4 for zero-parameter tools when schema coverage is complete.

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

Purpose3/5

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

The description states the tool's purpose as 'Request to have the validator exit', which is a clear verb+action. However, it doesn't specify what a 'validator' is in this context or differentiate from sibling tools like 'get_account_info' or 'send_transaction'. The purpose is understandable but lacks domain-specific clarity.

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. Given sibling tools include various read operations and actions like 'request_airdrop' or 'send_transaction', there's no indication of prerequisites, timing, or contextual triggers for validator exit requests.

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

Related 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/tywenk/mcp-sol'

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