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
Tools are mostly distinct: protocol operations are split into list, get, contracts, and summary, and name tools are clearly separated. However, identify_application and get_contract_role overlap since identify_application already returns the role, which could cause misselection.
All tools follow a consistent verb_noun pattern with snake_case, using verbs like get, identify, resolve, and search. The convention is uniform and predictable across the entire set.
10 tools is well within the ideal 3-15 range and fits the server's purpose of providing Algorand protocol, contract, asset, and name lookups. Each tool covers a distinct aspect without unnecessary bloat.
The surface covers protocol discovery, application/asset identification, contract roles, and name resolution (forward, reverse, search), which is comprehensive for a read-only static registry. Minor gaps exist, such as no direct list-all-assets or list-all-applications, but these are not critical dead ends.