Skip to main content
Glama

list_agents

View all registered agents and check their current availability status to determine which specialized tools are ready for task delegation.

Instructions

List all registered agents and their availability status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler logic for the 'list_agents' tool. It retrieves enabled agents, all registered agents, and their availability from the OrchestratorRegistry, then formats a text response listing each agent's status, availability, command, and arguments.
    elif name == "list_agents":
        # List registered agents and their availability
        enabled = self.registry.list_enabled()
        all_agents = list(self.registry.orchestrators.keys())
        availability = self.registry.validate_all()
    
        text = "Registered Agents:\n\n"
        for agent_name in all_agents:
            config = self.registry.get(agent_name)
            status = "✓ Enabled" if agent_name in enabled else "✗ Disabled"
            avail = "Available" if availability.get(agent_name) else "Not found in PATH"
            text += f"{agent_name}:\n"
            text += f"  Status: {status}\n"
            text += f"  Availability: {avail}\n"
            text += f"  Command: {config.command}\n"
            if config.args:
                text += f"  Args: {' '.join(config.args)}\n"
            text += "\n"
    
        return [TextContent(type="text", text=text)]
  • Tool registration in the list_tools() handler, defining the 'list_agents' tool with its name, description, and input schema (empty properties, no required arguments).
    Tool(
        name="list_agents",
        description="List all registered agents and their availability status",
        inputSchema={
            "type": "object",
            "properties": {},
        },
    ),
  • Input schema for the 'list_agents' tool: an object with no properties (no input parameters required).
    inputSchema={
        "type": "object",
        "properties": {},
    },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool lists agents and availability status but doesn't cover critical aspects like whether this is a read-only operation, potential rate limits, authentication requirements, or what the output format looks like. This leaves significant gaps for a tool that presumably interacts with agent data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It is front-loaded and appropriately sized for a simple tool, earning a perfect score for conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'availability status' entails, how the list is formatted, or any behavioral traits like safety or performance. For a tool that likely returns structured data about agents, more context is needed to guide the agent effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so there are no parameters to document. The description appropriately doesn't mention any parameters, which aligns with the schema. A baseline of 4 is applied since no parameters exist, and the description doesn't add unnecessary information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('List') and resource ('all registered agents and their availability status'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'discover_agents' or 'get_routing_guidance', which prevents a score of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'discover_agents' or 'get_routing_guidance'. It lacks any context about prerequisites, timing, or exclusions, leaving the agent with minimal usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

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/carlosduplar/multi-agent-mcp'

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