Skip to main content
Glama

list_agents

Retrieve and display all active agents connected to the Strands Agent MCP server for integration and management in MCP-compatible systems.

Instructions

list all available agents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_agents' tool. It returns a list of names of all registered agents by iterating over agent_registry.agent_entries. The @mcp.tool decorator registers it with FastMCP and provides the tool description/schema.
    @mcp.tool(description="list all available agents")
    def list_agents() -> List[str]:
        """
        List all registered agents
        """
        return [agent.name for agent in agent_registry.agent_entries]
  • Helper property on the Registry class that provides the list of all AgentEntry instances, which list_agents uses to extract agent names.
    @property
    def agent_entries(self) -> List[AgentEntry]:
        return [entry for entry in self._registry.values()]
  • Builds the agent registry by discovering agents from plugins, populating the agent_entries used by list_agents.
    def build_registry(discovered_plugins: Dict[str, ModuleType]) -> Registry:
        registry = Registry()
        for plugin_name, module in discovered_plugins.items():
            for agent_entry in module.build_agents():
                registry.register(agent_entry)
        return registry
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states what the tool does ('list all available agents') without revealing any behavioral traits such as whether it's read-only, if it requires authentication, how results are returned (e.g., pagination, format), or any rate limits. This is a significant gap for a tool with no annotation coverage.

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 'list all available agents' is a single, efficient sentence that front-loads the core action and resource. It has zero waste, making it appropriately sized for a simple listing tool. Every word earns its place by conveying the essential purpose without redundancy.

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 tool's simplicity (0 parameters, no output schema, no annotations), the description is minimal but incomplete. It lacks context about what 'agents' are, how the listing is structured (e.g., as a list, array, or paginated), and behavioral details. For a tool with no structured data to rely on, the description should provide more completeness to aid 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 tool has 0 parameters, and the schema description coverage is 100% (as there are no parameters to describe). The description doesn't need to add parameter semantics, so it meets the baseline of 4 for tools with no parameters. No additional value is required beyond stating the purpose.

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

Purpose3/5

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

The description 'list all available agents' clearly states the verb ('list') and resource ('agents'), making the purpose understandable. However, it lacks specificity about what 'agents' are in this context and doesn't distinguish from sibling tools like 'list_skills', which suggests a similar listing operation but for different resources. The description is functional but generic.

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. It doesn't mention sibling tools like 'execute_agent' (which likely performs actions with agents) or 'list_skills' (which lists a different resource), leaving the agent to infer usage based on tool names alone. There's no explicit context or exclusions provided.

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

Related 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/imgaray/strands-agents-mcp'

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