Skip to main content
Glama
5ajaki

Safe MCP Server

by 5ajaki

decodeTransactionData

Decode transaction data in hex format using Safe smart contract wallet APIs. Extract and interpret transaction details for clarity and analysis.

Instructions

Decode transaction data using Safe API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesTransaction data in hex format
toNoOptional contract address

Implementation Reference

  • The handler for the 'decodeTransactionData' tool. It performs a POST request to the Safe API's data-decoder endpoint with the transaction data (and optional 'to' address), handles specific HTTP errors, and returns the decoded transaction data as a JSON string.
    case "decodeTransactionData": {
      const { data, to } = args as any;
      const response = await fetch(`${SAFE_API_URL}/data-decoder/`, {
        method: "POST",
        headers: { "Content-Type": "application/json" },
        body: JSON.stringify({ data, to }),
      });
    
      if (!response.ok) {
        if (response.status === 404) {
          throw new McpError(
            ErrorCode.InternalError,
            "Cannot find function selector"
          );
        }
        if (response.status === 422) {
          throw new McpError(ErrorCode.InvalidParams, "Invalid data");
        }
        throw new McpError(
          ErrorCode.InternalError,
          `Decoder API error: ${response.statusText}`
        );
      }
    
      const decodedData = await response.json();
      return {
        content: [
          { type: "text", text: JSON.stringify(decodedData, null, 2) },
        ],
      };
    }
  • src/index.ts:143-160 (registration)
    Tool registration in the ListTools response, defining the name, description, and input schema for 'decodeTransactionData'.
    {
      name: "decodeTransactionData",
      description: "Decode transaction data using Safe API",
      inputSchema: {
        type: "object",
        properties: {
          data: {
            type: "string",
            description: "Transaction data in hex format",
          },
          to: {
            type: "string",
            description: "Optional contract address",
          },
        },
        required: ["data"],
      },
    },
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 the action ('decode') but doesn't describe what the tool returns, error conditions, rate limits, or authentication needs. This is a significant gap for a tool that likely processes sensitive transaction data.

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 for a simple tool and front-loads the core 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 the decoded output looks like, potential errors, or how it integrates with the Safe API context. For a data processing tool, this leaves critical gaps for an agent.

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 the schema already documents both parameters ('data' as hex format, 'to' as optional contract address). The description adds no additional parameter semantics beyond what the schema provides, meeting the baseline for high coverage.

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 ('decode') and resource ('transaction data'), and specifies the method ('using Safe API'), which provides a specific technical context. However, it doesn't explicitly differentiate from sibling tools like 'getMultisigTransaction' or 'getSafeTransactions', which appear to retrieve rather than decode data.

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, typical use cases, or how it differs from sibling tools like 'getMultisigTransaction' or 'getSafeTransactions', leaving the agent to infer usage context.

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