Skip to main content
Glama
Sign In
dexe-mcp

dexe-mcp

by edward-arinin-web-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Discover and list DAOs (subgraph)

dexe_read_dao_list
Read-onlyIdempotent

Discover DAOs by reading a paginated pools-subgraph list, search names case-insensitively, filter by chain ID, and get indexed chain rows with clear errors when a chain endpoint is unavailable.

Instructions

Read-only. Paginated DAO discovery via the pools subgraph; name search is case-insensitive, ordered by voter count descending. Pass chainId (chains with a pools endpoint here: 56; default 56); the reply echoes indexedChainId, never another chain's rows. No endpoint for a chain = an error that names the on-chain reads to use instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dexe_read_dao_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows per page.
queryNoName search (case-insensitive, empty = all)
offsetNoRows to skip (pagination).
chainIdNoChain to read from: 56 mainnet, 97 testnet. Needs an RPC for it. Default: the configured chain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.37.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior: descending voter-count ordering, case-insensitive matching, the indexedChainId echo, and the no-endpoint error path. It does not cover page-size limits or total-count behavior, keeping it mid-range.

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 tight sentences, front-loaded with the read-only guarantee and purpose before the parameter caveats. Nearly every clause carries information; only the chainId default clause is wasted because it duplicates and contradicts the schema.

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?

With no output schema, the description usefully discloses the shape-relevant facts an agent needs: the indexedChainId echo, ordering, and the failure mode for unsupported chains. Pagination correctness is adequately covered by the schema defaults for limit and offset.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema baseline is a 3; the description earns more by explaining that query matching is case-insensitive and that chainId must correspond to a pools endpoint. However its claim that chainId defaults to 56 conflicts with the schema's 'Default: the configured chain', which muddies rather than clarifies that parameter.

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 ('Paginated DAO discovery') plus the data source (pools subgraph), which separates it from registry-lookup or membership siblings. It stops short of naming a sibling it displaces, so it lands just under the top mark.

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?

Gives clear usage context: use it for paginated discovery, pass chainId for the chain you want, and expect an error naming on-chain alternatives when a chain has no pools endpoint. No explicit 'use X instead when...' routing to a named sibling, so not a 5.

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

Deploy Server

Other Tools