dexe-mcp

DAO TVL + activity stats time series

dexe_read_dao_stats

Read-onlyIdempotent

Read a DAO's time-series stats—TVL, members, proposals, and delegations—for a chosen period, with downsampling to keep results context-friendly.

Instructions

Read-only. Time series of DAO stats (tvl_usd, member counts, proposal counts, delegations) from the DeXe tracker. period is a human duration like '24 hours', '7 days', '1 months'. Backend-only — mainnets.

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

Input Schema

Name	Required	Description	Default
`period`	No	Duration window, e.g. '24 hours', '7 days', '1 months'	7 days
`chainId`	No	Chain for the backend lookup: 1 Ethereum, 56 BSC. Testnets are not indexed. Default: the configured chain.
`govPool`	Yes	GovPool / DAO address
`maxPoints`	No	Cap on returned data points; longer series are evenly downsampled (first and last points always kept). The tracker emits ~hourly points — '1 months' is ~740 raw points / ~650 KB, far beyond a usable context window.

Output Schema

Name	Required	Description
`data`	Yes
`period`	Yes
`points`	Yes	Raw point count returned by the tracker
`chainId`	Yes
`govPool`	Yes
`downsampled`	Yes
`returnedPoints`	Yes	Points in `data` after downsampling

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.37.1Nov 11, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful context beyond that: that the data comes from the DeXe tracker backend and is restricted to mainnets (explaining why testnet chain IDs fail). It says nothing about freshness/caching or failure modes the annotations don't cover.

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?

Three short sentences, front-loaded with the read-only safety note and the core purpose. The period format example is slightly redundant with the schema but is small. No filler.

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?

An output schema exists, so return values need not be explained, and the description still helpfully enumerates the stat families returned. Combined with the mainnet/backend constraint, an agent has enough to call it correctly. Only the missing sibling routing keeps it from 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%, so all four parameters including period format, chainId mapping and maxPoints downsampling are already documented. The description restates the period format and hints at the mainnet restriction on chainId, but adds no syntax or semantics the schema lacks. Baseline 3 is correct.

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 verb and resource: a time series of DAO stats (tvl_usd, member counts, proposal counts, delegations) from the DeXe tracker. An agent can tell this apart from point-in-time siblings like dexe_dao_info or dexe_read_dao_members because of the explicit 'time series' framing. It stops short of naming any sibling as an alternative.

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?

Usage is only implied by 'Time series of DAO stats' and the 'Backend-only — mainnets' constraint. There is no explicit when-to-use versus when-not-use, and no routing to a sibling such as dexe_dao_info for current snapshot values. Adequate but clearly incomplete.

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

Deploy Server