Skip to main content
Glama

Tx bundle plan

tx_bundle_plan
Read-onlyIdempotent

Exact-amount EVM approve + action (+ optional revoke) unsigned transaction bundle planner across 8 EVM chains: checks current allowance, balance, gas price, and sequential nonces; never requests unlimited approval and never touches private keys. $0.004 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "token": "<token>",
      "owner": "<owner>",
      "spender": "<spender>",
      "amount": "<amount>"
    },
    "name": "tx_bundle_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoethereum, base (default), arbitrum, optimism, polygon, bnb, arc or robinhood
ownerYessigning wallet address (0x + 40 hex)
tokenYesERC-20 token contract address (0x + 40 hex)
amountYestoken spend amount in human decimal units (or integer atomic base units with atomic=1)
atomicNoset "1" when amount is already in integer atomic base units
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
spenderYescontract address to approve and call (0x + 40 hex)
actionDataNooptional 0x hex calldata for the spender action transaction
revokeAfterNoset "1" to append a post-action approve(spender, 0) revocation tx
actionValueWeiNooptional non-negative integer wei value for the spender action transaction

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context on top: it never requests unlimited approval, never touches private keys, checks allowance/balance/gas/sequential nonces, and costs $0.004 per call via x402 (USDC on Arc/Base/Solana or XNT on X1). The two-call payment handshake is a behavioral detail an agent could not infer from the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with what the tool produces and its safety guarantees, then the payment mechanics. Dense but nearly every clause carries information. The pricing/token list is slightly in the way of the call-flow instruction, keeping it from a 5.

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

Completeness4/5

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

For a 10-parameter, no-output-schema tool, the description covers purpose, safety posture, cost and the payment protocol well. The main remaining gap is what the returned plan actually contains (tx list, nonces, gas figures) and whether it expires or can be replayed, which an agent would want before relying on it.

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 every parameter including `payment`, `atomic`, `revokeAfter` and `actionValueWei` is already documented in the schema. The description reinforces the exact-amount vs unlimited-approval distinction and the optional revoke, but adds no format or interaction detail beyond the structured fields. Baseline 3 applies.

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 names a specific verb and resource: plans an exact-amount EVM approve + action (+ optional revoke) unsigned transaction bundle across 8 chains. That is far more precise than the title 'Tx bundle plan'. It does not name a sibling such as evm_tx or arc_bundle_check to distinguish broadcast/execution from planning, so it falls short of a 5.

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?

Clear context is given for the two-phase invocation: call once without `payment` to get terms, sign with your own wallet, then call again with `payment`. It also implies the pre-flight role by listing allowance, balance, gas and nonce checks. It never states when NOT to use it or which sibling handles execution/broadcast, so no explicit exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources