Skip to main content
Glama

list_active_runs

Retrieve a list of all active runs to monitor ongoing processes and manage workflows efficiently within the ACP-MCP integration framework.

Instructions

List all active runs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'list_active_runs' tool. It iterates over the orchestrator's active_runs dictionary, extracts key information for each run, and returns a formatted JSON string listing all active runs.
    @mcp.tool()
    async def list_active_runs() -> str:
        """List all active runs"""
        
        runs_info = []
        for run_id, run in orchestrator.active_runs.items():
            runs_info.append({
                "run_id": run_id,
                "agent_name": run.agent_name,
                "status": run.status,
                "has_error": run.error is not None
            })
        
        return json.dumps(runs_info, indent=2)
  • Invocation of register_orchestrator_tools which defines and registers the list_active_runs tool (along with other orchestrator tools) to the FastMCP instance.
    register_orchestrator_tools(self.mcp, self.orchestrator)
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. 'List all active runs' implies a read-only operation but doesn't specify what constitutes an 'active run', whether results are paginated, or what the output format is. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 active runs' is a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse and understand immediately.

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 has 0 parameters, 100% schema coverage, and an output schema exists, the description is minimally adequate. However, with no annotations and siblings that might overlap (e.g., 'list_pending_interactions'), it lacks context about what 'active runs' are or how this tool fits into the broader workflow, leaving room for improvement.

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 there's no need for parameter documentation in the description. The description appropriately doesn't mention parameters, which is correct for a parameterless tool, earning a baseline score of 4.

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 'List all active runs' clearly states the verb ('List') and resource ('active runs'), making the tool's purpose immediately understandable. It doesn't distinguish from sibling tools like 'list_pending_interactions' or 'get_async_run_result', but the purpose is unambiguous on its own.

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. With siblings like 'list_pending_interactions' and 'get_async_run_result', there's no indication of how 'active runs' differ from 'pending interactions' or 'async runs', leaving the agent to guess based on tool names alone.

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/GongRzhe/ACP-MCP-Server'

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