Skip to main content
Glama
pc-style

MCP Goose Subagents Server

list_active_subagents

View currently active subagents and their operational status to monitor task delegation progress in development workflows.

Instructions

List currently active subagents and their status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'list_active_subagents' tool. It maps over active subagent sessions, computes durations, and returns a formatted text response listing all active sessions with their details.
    async listActiveSubagents() {
      const sessions = Array.from(this.activeSubagents.entries()).map(([id, session]) => ({
        session_id: id,
        task: session.task,
        agent_count: session.agents.length,
        execution_mode: session.execution_mode,
        status: session.status,
        start_time: session.startTime,
        end_time: session.endTime || null,
        duration: session.endTime 
          ? `${Math.round((session.endTime - session.startTime) / 1000)}s`
          : `${Math.round((new Date() - session.startTime) / 1000)}s (ongoing)`
      }));
    
      return {
        content: [
          {
            type: 'text',
            text: sessions.length > 0 
              ? `Active Subagent Sessions:\n\n${sessions.map(s => 
                  `Session: ${s.session_id}\n` +
                  `Task: ${s.task}\n` +
                  `Agents: ${s.agent_count} (${s.execution_mode})\n` +
                  `Status: ${s.status}\n` +
                  `Duration: ${s.duration}\n`
                ).join('\n')}`
              : 'No active subagent sessions.'
          }
        ]
      };
    }
  • src/index.js:119-125 (registration)
    Registration of the 'list_active_subagents' tool in the ListTools response, including name, description, and empty input schema.
      name: 'list_active_subagents',
      description: 'List currently active subagents and their status',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • Dispatch case in the CallToolRequestHandler that routes calls to the listActiveSubagents handler.
    case 'list_active_subagents':
      return await this.listActiveSubagents();
  • Input schema for the tool, which expects no parameters (empty properties).
    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 action ('List') but doesn't describe what 'active' means, how status is reported, whether this is a read-only operation, or any limitations like rate limits. This leaves significant gaps for a tool that might involve dynamic system state.

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 front-loads the core purpose with zero wasted words. It's appropriately sized for a simple listing tool with no parameters.

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 complexity of listing active subagents (which involves dynamic system state), no annotations, and no output schema, the description is incomplete. It doesn't explain what information is returned, how 'active' is defined, or any behavioral aspects, leaving the agent with insufficient context for reliable use.

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 with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter details, and it correctly implies no required inputs by not mentioning any, earning a baseline score for zero-parameter tools.

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 ('currently active subagents and their status'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'get_subagent_results' which might retrieve specific results rather than list active agents, but the distinction isn't explicit.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_subagent_results' or 'delegate_to_subagents'. The description implies usage for checking active subagents, but lacks explicit context, prerequisites, or exclusions.

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/pc-style/goose-mcp'

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