Skip to main content
Glama
bmorphism

Penumbra MCP Server

get_transaction

Retrieve detailed information about a specific transaction on the Penumbra blockchain using its unique hash. Facilitates privacy-preserving transaction queries on the Penumbra MCP Server.

Instructions

Get details of a specific transaction

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hashYesTransaction hash

Implementation Reference

  • The main handler function that executes the get_transaction tool logic, fetching transaction details by hash (currently mock data).
    private async getTransaction(hash: string) {
      try {
        // TODO: Implement actual transaction query
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                hash,
                status: "success",
                height: "1000000",
                timestamp: new Date().toISOString(),
                gasUsed: "50000",
                fee: "0.001"
              }, null, 2),
            },
          ],
        };
      } catch (error: unknown) {
        const errorMessage = error instanceof Error ? error.message : 'Unknown error occurred';
        return {
          content: [
            {
              type: 'text',
              text: `Error fetching transaction: ${errorMessage}`,
            },
          ],
          isError: true,
        };
      }
    }
  • src/index.ts:113-126 (registration)
    Registration of the get_transaction tool in the ListTools response, including name, description, and input schema.
    {
      name: 'get_transaction',
      description: 'Get details of a specific transaction',
      inputSchema: {
        type: 'object',
        properties: {
          hash: {
            type: 'string',
            description: 'Transaction hash',
          },
        },
        required: ['hash'],
      },
    },
  • Input schema defining the expected parameters for the get_transaction tool (hash: string).
    inputSchema: {
      type: 'object',
      properties: {
        hash: {
          type: 'string',
          description: 'Transaction hash',
        },
      },
      required: ['hash'],
    },
  • Dispatch handler in CallToolRequestSchema that validates input and calls the getTransaction method.
    case 'get_transaction':
      if (!request.params.arguments?.hash || typeof request.params.arguments.hash !== 'string') {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Transaction hash must be a string'
        );
      }
      return await this.getTransaction(request.params.arguments.hash);
    case 'get_dex_state':
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. It states the tool retrieves details but doesn't disclose behavioral traits like error handling, rate limits, authentication needs, or what 'details' include (e.g., status, timestamps). This leaves significant gaps for agent understanding.

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 appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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 doesn't explain what 'details' entail or potential behavioral aspects, making it inadequate for a tool that likely returns complex transaction data, leaving the agent with insufficient context.

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 description doesn't add meaning beyond the input schema, which has 100% coverage and clearly documents the 'hash' parameter. With high schema coverage, the baseline is 3, as the schema adequately handles parameter semantics without extra description.

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 verb ('Get') and resource ('details of a specific transaction'), making the purpose understandable. However, it doesn't differentiate this tool from potential sibling tools that might also retrieve transaction data, as none are listed among the siblings provided.

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. It doesn't mention prerequisites, context, or exclusions, such as whether it's for confirmed transactions only or if other tools handle batch queries.

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