Skip to main content
Glama

prepare_safe_tx_execute

DestructiveIdempotent

Build the final unsigned transaction to execute a Safe multisig payload, using implicit executor consent and on-chain approved hashes to meet the threshold.

Instructions

Build the final on-chain execTransaction UnsignedTx that lands a Safe (Gnosis Safe) multisig payload. The executor doesn't need to have pre-approved on-chain — when msg.sender is an owner, the Safe contract treats their inline (r=msg.sender, s=0, v=1) signature as implicit consent. So one of the threshold "signatures" can be the executor themselves; the rest come from the on-chain approvedHashes registry filled by previous prepare_safe_tx_propose / prepare_safe_tx_approve calls. Refuses to build the tx when the threshold isn't met (which would just revert at execute time). Resolves the SafeTx body from the local store first, falling back to Safe Transaction Service. Returns an UnsignedTx the executor broadcasts via send_transaction — the OUTER tx sends 0 ETH (the inner value, if any, is paid by the Safe from its own balance during the inner CALL).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
executorYes
safeAddressYes
chainNoethereum
safeTxHashYes
Behavior5/5

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

Describes implicit consent, fallback from local store to Safe Transaction Service, refusal when threshold not met, and outer tx behavior. Consistent with annotations (destructive, idempotent).

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?

Single dense paragraph covers all necessary info without redundancy. Technical but clear; every sentence adds value.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers inputs, behavior (implicit consent, fallback, refusal), output (UnsignedTx for send_transaction), and edge cases. No output schema needed since return type is well described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, description adds crucial context: executor's role (owner can sign implicitly), safeAddress for target, chain for network, safeTxHash as identifier from previous steps. Each parameter gets meaningful explanation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it builds the final on-chain execTransaction UnsignedTx for Safe multisig. It distinguishes from siblings by mentioning propose/approve steps and explains the process.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains when to use: after propose/approve, with threshold met, and mentions executor can be owner. Implicitly says not to use if threshold not met. Could be more explicit about alternatives.

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/szhygulin/vaultpilot-mcp'

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