Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_protocolsA

List all known Algorand protocols with type and description

get_protocolB

Get detailed information about a specific Algorand protocol by ID

get_protocol_contractsB

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NautilusOSS/UluAlgorandMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server