UluVoiMCP
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) |
| 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 10 tools
Each tool has a clearly distinct purpose with no overlap: get_contract_role focuses on contract roles, get_protocol and get_protocol_summary provide different levels of protocol detail, get_protocol_contracts lists contracts, get_protocols lists protocols, identify_application and identify_asset handle different resource types, and the name tools (resolve_name, reverse_resolve_address, search_names) are clearly scoped to static registry operations. An agent can easily distinguish between them based on their specific targets.
All tools follow a consistent verb_noun pattern with snake_case, using verbs like 'get', 'identify', 'resolve', 'reverse_resolve', and 'search' paired with specific nouns (e.g., contract_role, protocol, protocols, application, asset, name, address). This predictability makes it easy for an agent to understand the action and target from the name alone.
With 10 tools, the count is well-scoped for the domain of Voi ecosystem information and static name registry operations. Each tool serves a unique function, covering protocol discovery, contract details, asset/application identification, and name resolution without redundancy, making the set efficient and focused.
The tool set provides comprehensive coverage for querying Voi protocols, contracts, assets, applications, and static name registry data, with clear CRUD-like operations (e.g., get, list, identify, resolve). A minor gap exists as the server defers live name resolution to another MCP server (UluCoreMCP), but this is explicitly noted and does not hinder core functionality, allowing agents to work around it.