Skip to main content
Glama
bmorphism

Penumbra MCP Server

get_validator_set

Retrieve the current validator set information for the Penumbra blockchain, enabling users to access critical data about active validators for transactions and governance.

Instructions

Get the current validator set information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_validator_set' tool. It currently returns mock validator data with fields like address, votingPower, commission, and status. Includes error handling.
    private async getValidatorSet() {
      try {
        // TODO: Implement actual validator set query using Penumbra client
        // For now returning mock data until we integrate the proper client
        const mockValidators: ValidatorInfo[] = [
          {
            address: "penumbrav1xyz...",
            votingPower: "1000000",
            commission: "0.05",
            status: "active"
          }
        ];
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({ validators: mockValidators }, null, 2),
            },
          ],
        };
      } catch (error: unknown) {
        const errorMessage = error instanceof Error ? error.message : 'Unknown error occurred';
        return {
          content: [
            {
              type: 'text',
              text: `Error fetching validator set: ${errorMessage}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema for the 'get_validator_set' tool, which takes no parameters (empty object).
    inputSchema: {
      type: 'object',
      properties: {},
      required: [],
    },
  • src/index.ts:96-103 (registration)
    Registration of the 'get_validator_set' tool in the ListTools response, including name, description, and schema.
      name: 'get_validator_set',
      description: 'Get the current validator set information',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • src/index.ts:157-158 (registration)
    Dispatcher case in the CallToolRequest handler that routes to the getValidatorSet method.
    case 'get_validator_set':
      return await this.getValidatorSet();
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it 'gets' information (implying a read operation) but doesn't specify whether this requires authentication, has rate limits, returns real-time or cached data, or what format the information comes in. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence that communicates the core purpose without any wasted words. It's appropriately sized for a simple read operation and is front-loaded with the essential information.

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 lack of annotations and output schema, the description is insufficiently complete. It doesn't explain what 'validator set information' includes, whether it's paginated, how current 'current' is, or what the return format looks like. For a tool that presumably returns structured data about validators, more context is needed.

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 the schema already fully documents the parameter situation. The description appropriately doesn't mention parameters since none exist, which is correct. Baseline would be 4 for 0-parameter tools that don't mislead about parameters.

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 action ('Get') and the resource ('current validator set information'), making the purpose immediately understandable. It doesn't distinguish from sibling tools like get_chain_status or get_governance_proposals, but the verb+resource combination is specific enough for basic understanding.

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 like get_chain_status or get_dex_state. There's no mention of context, prerequisites, or exclusions, leaving the agent to infer usage based on tool names alone.

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/bmorphism/penumbra-mcp'

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