dexe-mcp

Execute a passed proposal

dexe_vote_build_execute

Read-only

Builds calldata for executing a DAO proposal through GovPool or an internal GovValidators proposal; it does not broadcast, so your wallet signs and submits the transaction.

Instructions

Builds calldata; does not broadcast. GovPool.execute(proposalId); scope:'internal' + govValidators builds GovValidators.executeInternalProposal(proposalId) (anyone may send once Succeeded). When an action calls GovSettings.addSettings the response carries an advisory naming the chains where the proposal passes the vote and then reverts here — read it before signing.

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": {
      "govPool": "<govPool>",
      "proposalId": "<proposalId>"
    },
    "name": "dexe_vote_build_execute"
  }
}

Input Schema

Name	Required	Description	Default
`scope`	No	'external' executes on GovPool; 'internal' on GovValidators (needs govValidators).	external
`voter`	No	Your address. When set, the deposit-lock warning is checked against your live power and shown only if your tokens really are locked.
`chainId`	No	Chain this payload targets: 56 mainnet, 97 testnet. Default: the configured chain.
`govPool`	Yes	DAO GovPool address (dexe_dao_registry_lookup).
`proposalId`	Yes	On-chain proposal id, 1-indexed decimal (dexe_proposal_list).
`govValidators`	No	Required for scope:'internal' (dexe_dao_info.helpers.validators)

Output Schema

Name	Required	Description
`payload`	Yes
`warnings`	No
`advisories`	No	Deprecated — use warnings.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.37.1Nov 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With readOnlyHint=true already declaring the safety profile, the description still adds real value: no broadcast, who may submit the resulting transaction, and the presence of an advisory in the response when GovSettings.addSettings is involved, including the caveat that the proposal can pass the vote on some chains and revert here. It does not describe the calldata payload format or signing flow, but the output schema can carry that.

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?

Front-loaded with the most decision-relevant fact ('Builds calldata; does not broadcast'), then the call mapping, then the advisory caveat. Dense with contract terminology but every clause carries operational meaning; only the addSettings sentence is heavy enough to slow parsing.

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 6-parameter build tool with full schema coverage, annotations and an output schema, the description covers the critical ambiguity (build vs broadcast), the internal-scope path, and the cross-chain advisory. Missing only an explicit statement of prerequisites such as the proposal needing to have Succeeded for the external path.

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 explains scope, voter, chainId, govPool, proposalId and govValidators. The description's restatement of scope:'internal' plus govValidators duplicates that, adding no format or behavioral nuance beyond the schema baseline.

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?

States a specific action: builds calldata for `GovPool.execute(proposalId)`, and explicitly clarifies it does not broadcast, which separates it from broadcast-style siblings such as dexe_proposal_vote_and_execute without naming them. The title ('Execute a passed proposal') is slightly at odds with the build-only nature, but the first sentence corrects that immediately.

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 clear context for the two modes: default external on GovPool, and scope:'internal' + govValidators for `GovValidators.executeInternalProposal`, including the precondition that anyone may send once the proposal has Succeeded. It stops short of an explicit 'use this instead of X when…' routing statement, so the choice against the broadcast sibling is inferred rather than stated.

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

Deploy Server