ulu-voi-mcp
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 |
|---|---|
| get_protocolsB | List all known Voi ecosystem protocols with type and description |
| get_protocolA | Get detailed information about a specific Voi ecosystem protocol by ID |
| get_protocol_contractsA | List all known application contracts for a Voi protocol |
| get_protocol_summaryA | Get a human-readable summary of a Voi protocol including its purpose, contracts, and assets |
| identify_applicationA | Identify a Voi application by ID — returns protocol, role, type, and description if known |
| identify_assetA | Identify a Voi asset by ID — returns name, symbol, type, protocol, and category if known |
| get_contract_roleA | Get the role and purpose of a specific contract on Voi (e.g. liquidity-pool, bridge, registry) |
| search_assetsB | Search known Voi assets by symbol, category, or protocol |
| resolve_nameA | Resolve an enVoi name (e.g. 'shelly.voi') to its address and metadata from the static registry. For live resolution, use UluCoreMCP's envoi tools. |
| reverse_resolve_addressA | Look up well-known enVoi names associated with a Voi address from the static registry. For live resolution, use UluCoreMCP's envoi tools. |
| search_namesA | Search the static enVoi name registry by pattern. For live search, use UluCoreMCP's envoi tools. |
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 11 tools
Most tools target distinct resources (protocols, apps, assets, names) with different query strategies. Minor overlap exists between get_protocol and get_protocol_summary, and between get_protocol_contracts and get_contract_role, but descriptions clarify their different intents.
Tool names follow a consistent verb_noun pattern (get_protocols, identify_asset, search_assets, resolve_name). Slight inconsistency in that several verbs are used (get, identify, search, resolve, reverse_resolve) but within each verb group the pattern is uniform.
11 tools is well-scoped for a read-only ecosystem registry. Each tool serves a distinct query need without redundancy or bloat.
The tool set covers the core read operations for protocols, contracts, applications, assets, and enVoi names. Minor gaps exist such as no direct 'get all assets' or 'get contract details by ID' beyond role lookup, but the domain is well served overall.