Skip to main content
Glama
pokt-network

Grove Public Endpoints MCP Server

Official
by pokt-network

get_cosmos_params

Retrieve chain parameters for Cosmos modules like staking, slashing, distribution, gov, and mint across mainnet or testnet networks.

Instructions

Get chain parameters for a Cosmos module

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
blockchainYesBlockchain name
moduleYesModule to query parameters for
networkNoNetwork type (defaults to mainnet)

Implementation Reference

  • Handler case for executing 'get_cosmos_params' tool: extracts arguments and delegates to CosmosService.getParams
    case 'get_cosmos_params': {
      const blockchain = args?.blockchain as string;
      const module = args?.module as 'staking' | 'slashing' | 'distribution' | 'gov' | 'mint';
      const network = (args?.network as 'mainnet' | 'testnet') || 'mainnet';
    
      const result = await cosmosService.getParams(blockchain, module, network);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
        isError: !result.success,
      };
    }
  • Tool schema definition including input schema for get_cosmos_params
    {
      name: 'get_cosmos_params',
      description: 'Get chain parameters for a Cosmos module',
      inputSchema: {
        type: 'object',
        properties: {
          blockchain: {
            type: 'string',
            description: 'Blockchain name',
          },
          module: {
            type: 'string',
            enum: ['staking', 'slashing', 'distribution', 'gov', 'mint'],
            description: 'Module to query parameters for',
          },
          network: {
            type: 'string',
            enum: ['mainnet', 'testnet'],
            description: 'Network type (defaults to mainnet)',
          },
        },
        required: ['blockchain', 'module'],
      },
    },
  • Core implementation: constructs REST API URL for module params and fetches data using fetchRest
    async getParams(
      blockchain: string,
      module: 'staking' | 'slashing' | 'distribution' | 'gov' | 'mint',
      network: 'mainnet' | 'testnet' = 'mainnet'
    ): Promise<EndpointResponse> {
      try {
        const baseUrl = this.getRestUrl(blockchain, network);
        const url = `${baseUrl}/cosmos/${module}/v1beta1/params`;
    
        return this.fetchRest(url);
      } catch (error) {
        return {
          success: false,
          error: error instanceof Error ? error.message : 'Failed to get Cosmos params',
        };
      }
    }
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 a 'Get' operation, implying read-only behavior, but does not clarify if it requires authentication, has rate limits, returns structured data, or handles errors. For a tool with 3 parameters and no output schema, this leaves significant gaps in understanding its behavior.

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 no wasted words. It front-loads the core purpose ('Get chain parameters for a Cosmos module') without unnecessary elaboration, 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 the tool's complexity (3 parameters, no annotations, no output schema), the description is insufficient. It does not explain what 'chain parameters' include, how results are formatted, or potential use cases. Without annotations or output schema, more detail is needed to guide effective tool selection and invocation.

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?

The input schema has 100% description coverage, clearly documenting each parameter (blockchain, module, network) with enums and defaults. The description adds no additional semantic context beyond what the schema provides, such as explaining module-specific parameter types or interactions. Baseline score of 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 states the tool 'Get chain parameters for a Cosmos module', which clearly indicates a read operation targeting specific blockchain parameters. However, it lacks specificity about what 'chain parameters' entail (e.g., governance settings, staking rules) and does not distinguish itself from sibling tools like 'get_cosmos_account' or 'get_cosmos_validators', which also retrieve Cosmos-related data but for different resources.

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 explicit guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, such as needing a valid blockchain name or module, nor does it compare to other tools like 'query_blockchain' or 'get_cosmos_proposal' that might retrieve related data. Usage is implied through the parameter context but not stated.

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/pokt-network/mcp'

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