Skip to main content
Glama
pc-style

MCP Goose Subagents Server

get_subagent_results

Retrieve completed task outputs from autonomous developer teams after delegating work to specialized agents for parallel or sequential execution.

Instructions

Get results from completed subagents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesSession ID to get results for

Implementation Reference

  • The handler function that retrieves subagent session results by session_id, checks if session exists, and returns formatted output including task details, status, output, and any errors.
    async getSubagentResults(args) {
      const { session_id } = args;
    
      if (!this.activeSubagents.has(session_id)) {
        throw new McpError(
          ErrorCode.InvalidRequest,
          `Session ${session_id} not found`
        );
      }
    
      const session = this.activeSubagents.get(session_id);
    
      return {
        content: [
          {
            type: 'text',
            text: `Subagent Session Results\n\nSession ID: ${session_id}\nTask: ${session.task}\nStatus: ${session.status}\nExecution Mode: ${session.execution_mode}\nAgents: ${session.agents.length}\n\n` +
                  `Start Time: ${session.startTime}\n` +
                  `End Time: ${session.endTime || 'Still running'}\n\n` +
                  `Output:\n${session.output || 'No output yet'}\n\n` +
                  `${session.error ? `Errors:\n${session.error}` : ''}`
          }
        ]
      };
    }
  • Tool schema definition in the listTools response, specifying the name, description, and input schema requiring a session_id.
    {
      name: 'get_subagent_results',
      description: 'Get results from completed subagents',
      inputSchema: {
        type: 'object',
        properties: {
          session_id: {
            type: 'string',
            description: 'Session ID to get results for'
          }
        },
        required: ['session_id']
      }
    }
  • src/index.js:155-156 (registration)
    Registration in the CallToolRequestHandler switch statement that dispatches calls to the getSubagentResults handler.
    case 'get_subagent_results':
      return await this.getSubagentResults(args);
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states the tool retrieves results but doesn't disclose details like whether it's read-only, if it requires specific permissions, how results are formatted, or potential errors (e.g., for invalid session IDs). This leaves significant gaps for an agent to understand operational traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/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 function without unnecessary words. However, it could be more front-loaded with key details (e.g., clarifying 'completed' subagents), but it avoids redundancy and is appropriately sized for a simple tool.

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 no annotations, no output schema, and a simple input schema, the description is incomplete. It doesn't explain what 'results' include (e.g., data format, success/failure status), behavioral aspects like error handling, or how it integrates with sibling tools. For a tool that likely returns structured data, this leaves the agent under-informed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with the single parameter 'session_id' documented in the schema as 'Session ID to get results for'. The description adds no additional meaning beyond this, such as format examples or context on where session IDs come from. Baseline 3 is appropriate since the schema adequately covers the parameter.

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 'Get results from completed subagents' clearly indicates the action (get) and target resource (results from subagents), but it's somewhat vague about what 'results' specifically entail. It doesn't differentiate from sibling tools like 'list_active_subagents' or 'delegate_to_subagents', leaving ambiguity about scope and relationship.

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 prerequisites (e.g., that subagents must be completed), exclusions, or how it relates to siblings like 'list_active_subagents' for active ones or 'delegate_to_subagents' for initiating tasks. Usage context is implied but not explicit.

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