dexe-mcp

Sign and broadcast a transaction

dexe_tx_send

Destructive

Broadcasts DeXe transaction payloads from build tools after signer setup, waits for confirmation, and refuses chain-ID mismatches or privileged GovUserKeeper calldata.

Instructions

Broadcasts when a signer is configured. Sends the TxPayload fields from any dexe_*build* tool and waits for confirmation. Pass chainId when several chains are configured, plus the payload's own chainId as payloadChainId — a mismatch REFUSES the send. Calldata with a privileged GovUserKeeper accounting selector is refused (hard block, no override).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dexe_tx_send"
  }
}

Input Schema

Name	Required	Description	Default
`to`	No	Destination contract address (or pass the builder's `payload` object)
`data`	No	ABI-encoded calldata (0x-prefixed hex)
`value`	No	Wei value as decimal string	0
`chainId`	No	Chain to broadcast on; needs an RPC for it. Default: the MCP's default chain.
`payload`	No	A dexe__build_ `payload` object verbatim ({to,data,value,chainId}). Fills to/data/value and payloadChainId when the flat fields are omitted.
`gasLimit`	No	Optional gas limit override (decimal string)
`signerKey`	No	Signer: omit = primary DEXE_PRIVATE_KEY (never an agent); 'agent<n>'/address = keyring.
`payloadChainId`	No	The TxPayload's own `chainId`, copied verbatim — a mismatch REFUSES the send.
`waitConfirmations`	No	Confirmations to wait (0 = fire-and-forget)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.37.1Nov 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=true; the description adds real behavioral facts the annotations cannot: it blocks and waits for confirmation, refuses a `chainId`/`payloadChainId` mismatch, hard-blocks privileged GovUserKeeper accounting selectors with no override, and defaults the signer to DEXE_PRIVATE_KEY. It stops short of covering failure modes like gas estimation or insufficient balance.

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?

Four tight sentences with the precondition front-loaded and the two hard-refusal rules grouped at the end. Dense but every sentence carries a distinct rule; minor awkwardness in the parenthetical-heavy chainId sentence.

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

Completeness3/5

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

For a 9-parameter, nested-object mutation with no output schema, it covers preconditions and refusal rules well but never says what comes back (tx hash? receipt?) or that `waitConfirmations: 0` is fire-and-forget, despite sibling tools dexe_tx_status/dexe_tx_approval_status existing to consume that result.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds meaning by explaining the two-chainId convention (`chainId` for broadcast target vs `payloadChainId` copied verbatim from the TxPayload) and the mismatch refusal consequence, which ties the fields together rather than restating them.

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?

States a specific verb and resource ('Sign and broadcast a transaction', 'Broadcasts when a signer is configured') and scopes it to inputs 'from any dexe_*_build_* tool', which distinguishes it from the builder siblings that produce payloads and from the status siblings that only poll them.

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?

Gives concrete usage conditions: it only broadcasts when a signer is configured, and `chainId` should be passed when several chains are configured. It does not explicitly name alternatives (e.g., use dexe_tx_status instead to poll), but the context needed to invoke it correctly is present.

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

Deploy Server