Skip to main content
Glama
Sign In
dexe-mcp

dexe-mcp

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

Session context

dexe_context
Read-onlyIdempotent

Orient a session by reporting configured chains, environment readiness, toolset visibility, and locally recorded DAOs/proposals; optionally include a wallet’s deposited voting power.

Instructions

Read-only. Session orientation — configured chains and the default, env readiness (RPC/IPFS/subgraph/backend), which toolsets are on or hidden and what the hidden ones unlock, and the DAOs/proposals recorded in this install's local state. Pass user to add that wallet's deposited power in the newest recorded DAO. Not needed once the DAO and chain are known. Persisted DAOs/proposals are WINDOWED; the *Total fields carry real counts.

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

Input Schema

NameRequiredDescriptionDefault
userNoWallet address: adds its deposited voting power in the newest recorded DAO (one extra RPC call).
daoLimitNoRecorded DAOs to return, newest first.
proposalLimitNoRecorded proposals to return, newest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.37.1

TDQS

A3.9/5.0
Behavior4/5

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

With readOnly/idempotent already declared, the description adds genuinely new behavior: persisted lists are WINDOWED while *Total fields carry real counts, and passing user triggers one extra RPC call. The cost hint and truncation semantics are exactly the kind of context annotations cannot convey. A minor redundancy is restating 'Read-only'.

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?

Front-loaded with the read-only stance and the enumeration of what is returned, then the parameter hint, then the 'when not needed' clause and the windowing caveat. The middle sentence is dense but every clause carries information; nothing is padding.

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 zero-required-parameter orientation tool with no output schema, the description covers the returned categories, the optional wallet enrichment, the windowing behavior with total counts, and an extra-call cost note. What is missing is only the precise response shape, which is acceptable given there is no output schema.

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 the baseline applies. The description only echoes the user parameter's effect (deposited power in the newest recorded DAO) rather than adding new meaning, and says nothing about daoLimit/proposalLimit beyond what the schema already states.

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 names concrete contents: configured chains and the default, env readiness (RPC/IPFS/subgraph/backend), toolset visibility, and locally recorded DAOs/proposals. This is clearly a session-orientation/state read, but it does not explicitly distinguish itself from near siblings such as dexe_get_config or dexe_read_settings, which an agent could reasonably confuse it with.

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?

It gives a clear exclusion — 'Not needed once the DAO and chain are known' — implying this is a first-call orientation step. It stops short of naming an alternative tool for any of the sub-needs it covers, so it is guidance without explicit routing.

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