UluAlgorandMCP
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_protocolsA | List all known Algorand protocols with type and description |
| get_protocolA | Get detailed information about a specific Algorand protocol by ID |
| get_protocol_contractsA | List all known application contracts for an Algorand protocol |
| get_protocol_summaryA | Get a concise agent-friendly summary of an Algorand protocol including its purpose, contracts, and assets |
| identify_applicationA | Identify an Algorand application by ID — returns protocol, role, type, and description if known |
| identify_assetA | Identify an Algorand asset by ID — returns name, symbol, type, protocol association, and tags if known |
| get_contract_roleA | Get the known protocol role for an Algorand application (e.g. amm-router, name-registry, lending-pool) |
| resolve_nameA | Resolve an Algorand name (e.g. 'example.algo') to its address and metadata from the static registry. For live resolution, use UluCoreMCP or NFDomains API. |
| reverse_resolve_addressA | Look up well-known Algorand names associated with an address from the static registry. For live resolution, use UluCoreMCP or NFDomains API. |
| search_namesA | Search the static Algorand name registry by pattern. Returns matching .algo names. |
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
Most tools have distinct purposes, but get_protocol and get_protocol_summary could be confused since both return protocol information, though summary is specifically agent-friendly. identify_application and get_contract_role also overlap slightly, but their descriptions clarify the different focus.
All tool names follow a consistent verb_noun pattern using clear verbs (get, identify, resolve, reverse_resolve, search). Naming is uniform with snake_case throughout, making the API predictable and easy to navigate.
With 10 tools, the server is well-scoped for a read-only Algorand registry. Each tool covers a distinct lookup or identification need without unnecessary bloat, fitting comfortably within the ideal range.
The tool set covers protocol discovery, application/asset identification, contract roles, and name resolution (forward, reverse, and search). Minor gaps exist such as no list_assets or list_applications, but the core lookup workflows are well-supported.