dexe-mcp

DAO overview — helpers, NFT contracts, validator count

dexe_dao_info

Read-onlyIdempotent

Reads a GovPool's core DAO details in one call—helper and NFT contract addresses, description URL, and live validator count—so you can verify configuration without multiple requests.

Instructions

Read-only. One multicall on a GovPool: helper addresses, NFT contract addresses, description URL, and live validator count.

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_dao_info"
  }
}

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	GovPool contract address

Output Schema

Name	Required	Description	Default
`govPool`	Yes
`helpers`	Yes
`nftContracts`	Yes
`descriptionURL`	Yes
`validatorsCount`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.37.1Nov 11, 2026

TDQS

A3.6/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 the safety profile is fully covered and the description's leading 'Read-only.' is largely redundant. The one genuinely additive fact is that the data comes from a single multicall on the GovPool, implying one RPC round trip. It says nothing about failure behavior for unsupported chains or invalid pool addresses.

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?

Two short sentences, front-loaded with the read-only nature and the multicall mechanism, with no filler. The opening 'Read-only.' duplicates an existing annotation, and 'One multicall on a GovPool' is compressed to the point of being slightly cryptic for a reader unfamiliar with the protocol.

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?

An output schema exists, so return-value documentation is not required, yet the description still enumerates the returned fields, which helps an agent decide to call it. With only two parameters, both documented in the schema, and full annotation coverage, nothing an agent needs in order to invoke this correctly is missing.

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%, with chainId already documenting 56/97 and the RPC requirement, so the schema carries the parameter burden. The description adds only that the operation targets a GovPool, mildly reinforcing that govPool is the pool contract address. 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?

It names a specific verb+resource combination: a read on a GovPool that returns helper addresses, NFT contracts, description URL, and validator count. An agent can tell it apart from dexe_read_dao_members or dexe_read_token_holders from the enumerated fields. It stops short of naming a sibling it is explicitly not, so it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

There is no explicit when-to-use or when-not-to-use statement and no named alternative such as dexe_read_dao_stats or dexe_read_settings. The implied usage — fetch a DAO's contract/helper configuration in a single call — is inferable from the field list and the 'one multicall' framing. That is implied guidance only, not routing guidance.

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

Deploy Server