Skip to main content
Glama
Sign In
dexe-mcp

dexe-mcp

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

Resolved server config

dexe_get_config
Read-onlyIdempotent

Reads the resolved DeXe configuration to show enabled chains, the default chain, subgraph coverage, backend API, and IPFS read gateways for setup checks.

Instructions

Read-only, local. The resolved read config: chain set and default chain, subgraph coverage per chain, the backend API and the IPFS read gateways.

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

Input Schema

NameRequiredDescriptionDefault
_placeholderNoUnused; tool takes no input.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.37.1

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context beyond them: it is 'local' (no network round-trip) and it itemizes exactly which config facets are returned, which is useful for an agent deciding whether a subsequent chain-specific call is needed.

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?

Two short sentences, with the read-only/local qualifier front-loaded ahead of the returned-field list. The phrasing is telegraphic rather than prose, but nothing is wasted and the structure is easy to scan.

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 carries the burden of saying what comes back, and it does so by listing the returned facets. The one gap is that terms like 'subgraph coverage per chain' and 'IPFS read gateways' are not explained, but for a zero-argument diagnostic read tool the definition is sufficient to call correctly.

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?

The tool effectively takes no input (one placeholder parameter, zero required, 100% schema description coverage), which is the baseline-4 case. The description correctly adds nothing about parameters and does not mislead the agent into supplying arguments.

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 the resource (resolved read config) and enumerates its contents: chain set, default chain, per-chain subgraph coverage, backend API, and IPFS read gateways. That is enough to distinguish it from most siblings (e.g. dexe_graph_query, dexe_ipfs_fetch), though it never explicitly contrasts with the nearer neighbours dexe_read_settings, dexe_context, or dexe_doctor.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use statement, no prerequisite, and no named alternative. 'Read-only, local' is a behavioral property rather than guidance about when an agent should call this instead of dexe_read_settings or dexe_context, so selection still requires inference.

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