dexe-mcp

Token sale position for a wallet (old name)

dexe_otc_buyer_status

Read-onlyIdempotent

Reads a buyer's OTC token sale position status for specified tiers and proposal, using an optional whitelist; deprecated alias of dexe_read_token_sale_position.

Instructions

Read-only. Deprecated alias of dexe_read_token_sale_position (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": {
      "tokenSaleProposal": "<tokenSaleProposal>",
      "tierIds": "<tierIds>",
      "user": "<user>"
    },
    "name": "dexe_otc_buyer_status"
  }
}

Input Schema

Name	Required	Description
`user`	Yes	Buyer address to report state for.
`chainId`	No	Chain to read from: 56 mainnet, 97 testnet. Needs an RPC for it. Default: the configured chain.
`tierIds`	Yes	Tier ids to report on, decimal strings (1 to 50).
`whitelists`	No	Optional per-tier whitelist (for MerkleWhitelist proof generation).
`tokenSaleProposal`	Yes	TokenSaleProposal helper address

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.37.1Nov 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the leading 'Read-only.' adds nothing. The genuinely additive disclosure is the deprecation status and the guarantee of identical input/output to the canonical tool, which shapes agent behavior in a way no annotation captures.

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?

A single front-loaded sentence: safety/deprecation status first, canonical replacement named with version, contract equivalence last. No filler, nothing an agent must scan past.

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 five-parameter pure-read alias with full schema coverage and no output schema, naming the canonical tool and asserting identical inputs/outputs is close to complete. A brief note on whether any response metadata differs (e.g., deprecation warnings) would close the remaining gap.

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, tierIds, whitelists, and user, so the schema carries the parameter burden. 'Same input and output' correctly signals the parameter contract is unchanged, but adds no meaning beyond what the schema already documents.

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_sale_position, which lets an agent locate the actual verb+resource (reading a token sale position for a wallet) via the canonical tool. It distinguishes this entry from siblings by pointing to the exact equivalent, though it never states the purpose directly in its own words.

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?

The deprecation notice plus the rename version (0.36.0) effectively routes an agent to dexe_read_token_sale_position instead of this tool. It stops short of an explicit 'do not call this; call X' instruction or any statement of when the alias is still legitimate (e.g., pinned older versions).

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

Deploy Server