Skip to main content
Glama
bmorphism

Penumbra MCP Server

get_chain_status

Retrieve current blockchain status such as block height and chain ID for the Penumbra network to monitor and verify chain activity.

Instructions

Get current chain status including block height and chain ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The private async getChainStatus() method implements the core logic for the get_chain_status tool, returning a mock ChainStatus object with height, chainId, timestamp, and blockHash.
    private async getChainStatus() {
      try {
        // TODO: Implement actual chain status query
        const mockStatus: ChainStatus = {
          height: "1000000",
          chainId: CONFIG.chain.chainId,
          timestamp: new Date().toISOString(),
          blockHash: "0x..."
        };
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(mockStatus, null, 2),
            },
          ],
        };
      } catch (error: unknown) {
        const errorMessage = error instanceof Error ? error.message : 'Unknown error occurred';
        return {
          content: [
            {
              type: 'text',
              text: `Error fetching chain status: ${errorMessage}`,
            },
          ],
          isError: true,
        };
      }
    }
  • src/index.ts:104-112 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining the name, description, and input schema (empty object) for get_chain_status.
    {
      name: 'get_chain_status',
      description: 'Get current chain status including block height and chain ID',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • src/index.ts:159-160 (registration)
    Dispatch logic in the CallToolRequestSchema handler that calls getChainStatus() when the tool name is 'get_chain_status'.
    case 'get_chain_status':
      return await this.getChainStatus();
  • TypeScript interface defining the structure of the chain status response returned by the tool.
    interface ChainStatus {
      height: string;
      chainId: string;
      timestamp: string;
      blockHash: string;
    }
Behavior2/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 of behavioral disclosure. It states the tool retrieves information ('Get'), implying a read-only operation, but doesn't clarify aspects like whether it requires authentication, has rate limits, returns real-time or cached data, or what happens on errors. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 front-loads the purpose ('Get current chain status') and adds specifics ('including block height and chain ID'). There is no wasted verbiage or redundancy, making it highly concise and well-structured for quick comprehension.

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

Completeness3/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, no output schema), the description is adequate for a basic read operation. It specifies what information is retrieved, which helps the agent understand the output. However, without annotations or an output schema, it lacks details on behavioral traits (e.g., error handling) and return format, leaving some gaps in completeness.

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, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, but it correctly indicates no inputs are required. Baseline is 4 for zero parameters, as the description aligns with the schema's lack of inputs.

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 chain status'), specifying what information is included ('block height and chain ID'). It distinguishes from siblings like get_dex_state or get_transaction by focusing on chain-level metadata rather than DEX data, governance, or specific transactions. However, it doesn't explicitly contrast with all siblings (e.g., get_validator_set).

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 implies usage for retrieving chain metadata, but it doesn't state when to prefer this over other tools (e.g., for checking chain health vs. querying transactions) or mention any prerequisites. This leaves the agent to infer context from the tool name 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