Skip to main content
Glama
5ajaki

Safe MCP Server

by 5ajaki

getMultisigTransaction

Retrieve detailed information about a specific multisig transaction using its unique transaction hash with the Safe MCP Server.

Instructions

Get details of a specific multisig transaction

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
safeTxHashYesSafe transaction hash

Implementation Reference

  • Handler logic for the getMultisigTransaction tool. Extracts safeTxHash from arguments, fetches transaction details from the Safe API endpoint `/multisig-transactions/${safeTxHash}/`, and returns the JSON-formatted response.
    case "getMultisigTransaction": {
      const { safeTxHash } = args as any;
      const data = await this.fetchSafeApi(
        `/multisig-transactions/${safeTxHash}/`
      );
      return {
        content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
      };
    }
  • src/index.ts:129-142 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining the name, description, and input schema for getMultisigTransaction.
    {
      name: "getMultisigTransaction",
      description: "Get details of a specific multisig transaction",
      inputSchema: {
        type: "object",
        properties: {
          safeTxHash: {
            type: "string",
            description: "Safe transaction hash",
          },
        },
        required: ["safeTxHash"],
      },
    },
  • Input schema definition for the getMultisigTransaction tool, specifying the required safeTxHash parameter.
    inputSchema: {
      type: "object",
      properties: {
        safeTxHash: {
          type: "string",
          description: "Safe transaction hash",
        },
      },
      required: ["safeTxHash"],
    },
  • Helper method used by the handler to make authenticated API calls to the Safe API, handling URL construction, query params, error handling, and JSON parsing.
    private async fetchSafeApi(
      endpoint: string,
      params?: Record<string, string>
    ): Promise<any> {
      const url = new URL(`${SAFE_API_URL}${endpoint}`);
      if (params) {
        Object.entries(params).forEach(([key, value]) => {
          url.searchParams.append(key, value);
        });
      }
    
      const response = await fetch(url.toString());
      if (!response.ok) {
        throw new McpError(
          ErrorCode.InternalError,
          `Safe API error: ${response.statusText}`
        );
      }
      return response.json();
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Get details' implies a read-only operation, it doesn't explicitly confirm this or describe what details are returned, error conditions, or any rate limits. 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 directly states the tool's purpose with zero wasted words. It's appropriately sized for a simple lookup tool and front-loads 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 incomplete for a tool that retrieves transaction details. It doesn't explain what details are returned, potential error cases, or how this differs from sibling tools. For a tool with no structured behavioral or output information, the description should provide more 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 schema description coverage is 100%, with the single parameter 'safeTxHash' clearly documented in the schema. The description doesn't add any meaning beyond what the schema provides (e.g., it doesn't explain hash format or where to obtain it). With high schema coverage, the baseline score of 3 is appropriate.

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 details') and target resource ('specific multisig transaction'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'getSafeTransactions' (which likely retrieves multiple transactions), missing the opportunity to clarify this is for retrieving a single transaction by hash.

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 the sibling tools 'decodeTransactionData' or 'getSafeTransactions', nor does it specify prerequisites like needing a transaction hash. The agent must infer usage context from the tool name and parameter 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/5ajaki/safe-mcp-server'

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