dexe-mcp

Default + internal proposal settings for a DAO

dexe_read_settings

Read-onlyIdempotent

Reads a DAO GovPool's governance settings—quorum, voting duration, execution delay, and minimum votes for creating or voting—to inspect proposal rules.

Instructions

Read-only. Reads GovSettings.getDefaultSettings() and getInternalSettings() for the DAO at govPool — quorum, duration, executionDelay, minVotesForCreating/Voting.

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>"
    },
    "name": "dexe_read_settings"
  }
}

Input Schema

Name	Required	Description	Default
`chainId`	No	Chain to read from: 56 mainnet, 97 testnet. Needs an RPC for it. Default: the configured chain.
`govPool`	Yes	DAO GovPool address (dexe_dao_registry_lookup).

Output Schema

Name	Required	Description	Default
`govPool`	Yes
`settings`	Yes
`defaultSettings`	No
`internalSettings`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.37.1Nov 11, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so 'Read-only.' adds nothing beyond structured data. What the description does add is the specific source of the data (two named contract getters) and the two setting sets (default vs internal), which helps an agent understand what is being read. It does not mention chain/RPC dependency handling, which is left entirely to 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?

A single compact sentence with the field list appended after a dash, front-loaded and free of filler. Minor waste: 'Read-only.' duplicates the readOnlyHint annotation rather than earning its place.

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 two-parameter read tool with full schema coverage and an output schema covering return values, the description supplies what is needed to call it correctly (which contract getters, which DAO scope). The remaining gap is usage context — when in a workflow to fetch these settings — which is why it is not a 5.

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%: `chainId` documents 56/97 and the RPC requirement, and `govPool` documents the DAO address and points at dexe_dao_registry_lookup. The description mentions `govPool` only as the scope of the read, adding no semantics beyond the schema, so the 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 (reads) and resource (default and internal governance/proposal settings for the DAO at `govPool`) and even cites the contract getters `GovSettings.getDefaultSettings()` / `getInternalSettings()`. Enumerating quorum, duration, executionDelay and minVotesForCreating/Voting makes it distinguishable from aggregate siblings like dexe_read_dao_stats, though no sibling is named explicitly.

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?

There is no when-to-use or when-not-to-use guidance: nothing says to call this before creating a proposal, before voting, or instead of dexe_dao_info. The only framing is 'Read-only.', which describes safety rather than usage context.

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

Deploy Server