Skip to main content
Glama
zebbern

agloop-mcp

by zebbern

agloop_list_agents

Retrieve all agent names from the .github/agents/ directory to identify available automation resources within the AgLoop framework.

Instructions

List all available agent names in .github/agents/.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler for the 'agloop_list_agents' tool, which lists available agents using the StateManager's list_agents method.
    @mcp.tool()
    def agloop_list_agents() -> str:
        """List all available agent names in .github/agents/."""
        agents = _sm().list_agents()
        return json.dumps(agents, indent=2)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action but doesn't disclose behavioral traits such as whether this is a read-only operation, if it requires authentication, potential rate limits, or how results are returned (e.g., format, pagination). The description is minimal and misses key operational details.

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 with no wasted words. It is front-loaded and appropriately sized for a simple listing tool, making it easy to parse quickly.

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

Completeness3/5

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

Given the tool's low complexity (0 parameters, simple listing operation) and the presence of an output schema (which handles return values), the description is somewhat complete. However, with no annotations and minimal behavioral disclosure, it lacks context on operational aspects like safety or performance, making it adequate but with gaps.

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 schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add param info, which is appropriate here. Baseline is 4 for zero parameters, as there's nothing to compensate for.

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 ('agent names'), specifying the location ('.github/agents/'). It distinguishes from siblings like 'agloop_get_agent_info' by focusing on listing names rather than retrieving detailed info. However, it doesn't explicitly contrast with 'agloop_list_tasks', which might be a similar listing operation for a different resource.

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

Usage Guidelines3/5

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

The description implies usage when needing to see available agents, but provides no explicit guidance on when to use this tool versus alternatives like 'agloop_get_agent_info' for detailed info or 'agloop_list_tasks' for other listings. It lacks prerequisites or exclusions, leaving usage context inferred rather than stated.

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/zebbern/agloop-mcp'

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