Skip to main content
Glama
buildwithgrove

Grove's MCP Server for Pocket Network

get_cosmos_validator

Retrieve validator details for Cosmos-based blockchains using Grove's MCP Server for Pocket Network. Provide blockchain name and validator address to access specific validator information.

Instructions

Get specific validator details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
blockchainYesBlockchain name
validatorAddressYesValidator address
networkNoNetwork type (defaults to mainnet)

Implementation Reference

  • MCP tool handler that extracts parameters from tool arguments and calls CosmosService.getValidator to execute the tool logic
    case 'get_cosmos_validator': {
      const blockchain = args?.blockchain as string;
      const validatorAddress = args?.validatorAddress as string;
      const network = (args?.network as 'mainnet' | 'testnet') || 'mainnet';
    
      const result = await cosmosService.getValidator(blockchain, validatorAddress, network);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
        isError: !result.success,
      };
    }
  • Input schema definition for the get_cosmos_validator tool, specifying parameters like blockchain, validatorAddress, and optional network
    {
      name: 'get_cosmos_validator',
      description: 'Get specific validator details',
      inputSchema: {
        type: 'object',
        properties: {
          blockchain: {
            type: 'string',
            description: 'Blockchain name',
          },
          validatorAddress: {
            type: 'string',
            description: 'Validator address',
          },
          network: {
            type: 'string',
            enum: ['mainnet', 'testnet'],
            description: 'Network type (defaults to mainnet)',
          },
        },
        required: ['blockchain', 'validatorAddress'],
      },
    },
  • src/index.ts:98-98 (registration)
    Registers the Cosmos tools (including get_cosmos_validator) by including the result of registerCosmosHandlers in the server's tool list for ListToolsRequest
    ...registerCosmosHandlers(server, cosmosService),
  • Core helper function that constructs the REST API URL and fetches specific validator details from the Cosmos staking endpoint
    async getValidator(
      blockchain: string,
      validatorAddress: string,
      network: 'mainnet' | 'testnet' = 'mainnet'
    ): Promise<EndpointResponse> {
      try {
        const baseUrl = this.getRestUrl(blockchain, network);
        const url = `${baseUrl}/cosmos/staking/v1beta1/validators/${validatorAddress}`;
    
        return this.fetchRest(url);
      } catch (error) {
        return {
          success: false,
          error: error instanceof Error ? error.message : 'Failed to get Cosmos validator',
        };
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a read operation ('get'), implying non-destructive, but doesn't cover permissions, rate limits, error handling, or return format. This is inadequate for a tool with potential complexity in blockchain contexts.

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 with zero waste. It's front-loaded and appropriately sized for its purpose, making it easy to parse quickly.

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 no annotations and no output schema, the description is incomplete. It lacks behavioral context, return value explanation, and differentiation from siblings, which is insufficient for a tool that likely returns complex validator data in a blockchain ecosystem.

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

Parameters3/5

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

Schema description coverage is 100%, so parameters are documented in the schema. The description adds no additional meaning beyond implying 'specific' via validatorAddress, but doesn't clarify parameter interactions or semantics. Baseline 3 is appropriate as the schema does the heavy lifting.

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 'Get specific validator details' clearly states the action (get) and resource (validator details), making the purpose understandable. However, it doesn't specify what 'details' include or differentiate it from sibling tools like 'get_cosmos_validators' (plural), leaving the scope vague.

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. It doesn't mention prerequisites, context for selecting it over 'get_cosmos_validators', or any exclusions, leaving the agent without usage direction.

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/buildwithgrove/mcp-pocket'

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