Skip to main content
Glama
lordstyled55

MCP Goose Subagents Server

by lordstyled55

list_active_subagents

View currently active subagents and their operational status to monitor task delegation across specialized developer roles.

Instructions

List currently active subagents and their status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that retrieves and formats a list of active subagent sessions, including session details like ID, task, agent count, status, and duration.
    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.'
          }
        ]
      };
    }
  • Tool schema definition including name, description, and input schema (empty properties).
    {
      name: 'list_active_subagents',
      description: 'List currently active subagents and their status',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • src/index.js:153-154 (registration)
    Registration in the CallToolRequestSchema switch statement that routes calls to the handler method.
    case 'list_active_subagents':
      return await this.listActiveSubagents();
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 active subagents and their status, implying a read-only operation, but doesn't specify whether this requires permissions, how status is defined, or what the return format looks like. This leaves significant gaps for a tool with zero 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 is a single, efficient sentence that directly states the tool's purpose without any wasted words. It's front-loaded and 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.

Completeness3/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 adequate as a basic listing operation. However, it lacks details on output format, status definitions, or how it relates to sibling tools, which could help the agent use it more effectively in context.

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 appropriately doesn't add parameter details, as none are needed, earning a baseline score of 4 for not introducing 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 ('currently active subagents and their status'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_subagent_results' or explain how this differs from 'delegate_to_subagents', which prevents a perfect score.

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 'get_subagent_results' or 'delegate_to_subagents'. There's no mention of prerequisites, context, 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/lordstyled55/goose-mcp'

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