dexe-mcp

List a DAO's token sale tiers (old name)

dexe_otc_list_sales_for_dao

Read-onlyIdempotent

Lists OTC token sales for a DeXe DAO by reading on-chain sale data; use it to inspect active or past sales before voting, buying, or managing proposals.

Instructions

Read-only. Deprecated alias of dexe_read_token_sales (renamed in 0.36.0); same input and output.

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

Input Schema

Name	Required	Description
`chainId`	No	Chain to read from: 56 mainnet, 97 testnet. Needs an RPC for it. Default: the configured chain.
`govPool`	Yes	GovPool address
`tokenSaleProposal`	No	TokenSaleProposal helper address. Omit when the local state records it; otherwise dexe_dao_predict_addresses or the deploy receipt.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.37.1Nov 11, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so 'Read-only' in the description is redundant. The value added is the deprecation status and the 0.36.0 rename, which no annotation captures. It does not say whether the alias will be removed or behaves identically forever.

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

Conciseness5/5

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

One short sentence with zero filler, front-loading the read-only nature and the deprecation in the first clause. Nothing could be removed without losing information.

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 deprecated alias with full schema coverage and a complete annotation set, this is nearly complete: the agent knows what it does, that it is superseded, and that I/O matches the replacement. A removal timeline or explicit 'use dexe_read_token_sales' directive is the only missing piece.

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%, including chainId, govPool and the fallback guidance for tokenSaleProposal, so the schema carries all parameter meaning. The description adds nothing beyond 'same input and output', which is the baseline-3 case.

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 identifies the tool as a deprecated alias of dexe_read_token_sales with identical input and output, and the title names the resource (token sale tiers). An agent can tell exactly what it does and which sibling it duplicates, though the purpose is expressed by reference rather than directly.

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?

Calling it a 'deprecated alias' plus naming dexe_read_token_sales gives clear implicit routing: prefer the new name. It stops short of an explicit 'use X instead' instruction or a statement of whether this alias is safe to keep calling.

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

Deploy Server