Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AGENTZONE_API_KEYNoAPI key for authenticated endpoints (e.g., register agents, report payments)
AGENTZONE_BASE_URLNoBase URL for AgentZone APIhttps://agentzone.fun

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_agentsC

Search for AI agents by query, capability, chain, or trust threshold

get_agentC

Get detailed information about a specific agent by wallet address

discover_agentsC

Machine-to-machine agent discovery with filtering

get_analyticsC

Get network analytics and time-series data

get_statsB

Get quick network statistics

report_paymentC

Report an x402 payment transaction (requires API key)

register_agentC

Register a new AI agent (requires API key)

check_healthB

Check AgentZone API health status

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 8 tools

Disambiguation4/5

Most tools have distinct purposes, but get_analytics and get_stats could cause some confusion as both relate to network data. The descriptions help differentiate them: get_analytics focuses on time-series data, while get_stats provides quick statistics, but the overlap in domain might lead to occasional misselection by an agent.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case, such as check_health, discover_agents, and register_agent. This predictability makes it easy for agents to understand and use the tools without confusion from mixed conventions.

Tool Count5/5

With 8 tools, the count is well-scoped for the AgentZone domain, covering key operations like health checks, agent discovery, registration, and analytics. Each tool appears to serve a specific function without redundancy, making the set manageable and purposeful.

Completeness4/5

The tool surface covers core workflows for agent management and network interaction, including discovery, registration, and analytics. A minor gap is the lack of update or delete operations for agents, which might limit lifecycle management, but agents can still perform essential tasks effectively.

Maintenance

ActivityInactive
ResponsivenessNo issues