Dysnomia Ecosystem Navigator — MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_ecosystemA | List all known Dysnomia ecosystem contracts with their addresses, categories, and descriptions. Good starting point for exploration. |
| get_contract_stateA | Read the current on-chain state of any Dysnomia contract — balances, supply, ownership, minting status. Accepts a contract name (META, RING, etc.) or raw address. |
| trace_minterA | Trace a minter address across the Dysnomia ecosystem — check its terraforming status, linked tokens, balances in each core contract, and progression toward apparition. |
| query_qingA | Look up QING territory data — ownership, state, metadata. Can query by territory ID or by owner address to find all their territories. |
| debug_callA | Simulate a contract call (eth_call) without sending a transaction. Surfaces revert reasons, out-of-gas, division-by-zero, and other errors BEFORE you spend gas. Great for debugging Beat() and other state-changing functions. |
| map_relationshipsB | Map the dependency and ownership relationships between Dysnomia contracts. Shows which contracts own, mint for, or reference each other — useful for understanding the ecosystem graph. |
| search_eventsB | Search on-chain event logs across Dysnomia contracts. Filter by contract, event topic, address, or block range. Useful for tracking minting activity, transfers, Beat() calls, and terraforming events. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clear, non-overlapping purpose: debug_call simulates calls, map_relationships graphs contract dependencies, list_ecosystem enumerates contracts, get_contract_state reads specific contract state, trace_minter follows minters, query_qing looks up QING territories, and search_events scans event logs. There is minimal ambiguity between tools.
All tool names follow a consistent verb_noun snake_case pattern (debug_call, map_relationships, list_ecosystem, get_contract_state, trace_minter, query_qing, search_events). The verbs are distinct and accurately describe each operation, and no naming conventions are mixed.
Seven tools is well within the ideal 3-15 range for an ecosystem explorer. The count is neither too sparse nor overwhelming, and each tool provides a meaningful capability without redundancy.
The tool set covers the full read-only exploration lifecycle for the Dysnomia ecosystem: discovering contracts, inspecting state, simulating calls, mapping relationships, tracing minters, querying territories, and searching events. No obvious essential operation is missing for the apparent domain.