AgentZone MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTZONE_API_KEY | No | API key for authenticated endpoints (e.g., register agents, report payments) | |
| AGENTZONE_BASE_URL | No | Base URL for AgentZone API | https://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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
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.
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.
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.
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.