Skip to main content
Glama
lordstyled55

MCP Goose Subagents Server

by lordstyled55

delegate_to_subagents

Delegate development tasks to specialized autonomous subagents for parallel or sequential execution across roles like backend developers and QA engineers.

Instructions

Delegate tasks to Goose CLI subagents for autonomous development

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesThe development task to delegate to subagents
agentsYesArray of subagents to create
execution_modeNoHow to execute the subagentsparallel
working_directoryNoWorking directory for the subagents (defaults to current directory)

Implementation Reference

  • The primary handler function for the 'delegate_to_subagents' tool. Parses arguments, generates a delegation prompt using createDelegationPrompt, spawns a Goose CLI process via executeGoose, tracks the session in activeSubagents, and returns a success message with session ID.
    async delegateToSubagents(args) {
      const { task, agents, execution_mode = 'parallel', working_directory = process.cwd() } = args;
      const sessionId = uuidv4();
    
      // Ensure Goose alpha features are enabled
      process.env.ALPHA_FEATURES = 'true';
    
      try {
        // Create the delegation prompt for Goose
        const delegationPrompt = this.createDelegationPrompt(task, agents, execution_mode);
        
        // Execute Goose with the delegation prompt
        const gooseProcess = await this.executeGoose(delegationPrompt, working_directory, sessionId);
        
        this.activeSubagents.set(sessionId, {
          task,
          agents,
          execution_mode,
          status: 'running',
          startTime: new Date(),
          process: gooseProcess
        });
    
        return {
          content: [
            {
              type: 'text',
              text: `Successfully delegated task to ${agents.length} subagents in ${execution_mode} mode.\n\nSession ID: ${sessionId}\nTask: ${task}\n\nSubagents created:\n${agents.map(agent => `- ${agent.role}: ${agent.instructions}`).join('\n')}\n\nUse get_subagent_results with session_id "${sessionId}" to retrieve results when complete.`
            }
          ]
        };
      } catch (error) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to delegate to subagents: ${error.message}`
        );
      }
    }
  • Input schema definition for the 'delegate_to_subagents' tool, specifying required task and agents, optional execution_mode and working_directory.
    inputSchema: {
      type: 'object',
      properties: {
        task: {
          type: 'string',
          description: 'The development task to delegate to subagents'
        },
        agents: {
          type: 'array',
          items: {
            type: 'object',
            properties: {
              role: {
                type: 'string',
                description: 'Agent role (e.g., backend_developer, frontend_developer, qa_engineer)'
              },
              instructions: {
                type: 'string',
                description: 'Specific instructions for this agent'
              },
              recipe: {
                type: 'string',
                description: 'Optional recipe name to use for this agent'
              }
            },
            required: ['role', 'instructions']
          },
          description: 'Array of subagents to create'
        },
        execution_mode: {
          type: 'string',
          enum: ['parallel', 'sequential'],
          default: 'parallel',
          description: 'How to execute the subagents'
        },
        working_directory: {
          type: 'string',
          description: 'Working directory for the subagents (defaults to current directory)'
        }
      },
      required: ['task', 'agents']
    }
  • src/index.js:41-86 (registration)
    Tool registration in the ListToolsRequestSchema handler, defining name, description, and input schema for 'delegate_to_subagents'.
    {
      name: 'delegate_to_subagents',
      description: 'Delegate tasks to Goose CLI subagents for autonomous development',
      inputSchema: {
        type: 'object',
        properties: {
          task: {
            type: 'string',
            description: 'The development task to delegate to subagents'
          },
          agents: {
            type: 'array',
            items: {
              type: 'object',
              properties: {
                role: {
                  type: 'string',
                  description: 'Agent role (e.g., backend_developer, frontend_developer, qa_engineer)'
                },
                instructions: {
                  type: 'string',
                  description: 'Specific instructions for this agent'
                },
                recipe: {
                  type: 'string',
                  description: 'Optional recipe name to use for this agent'
                }
              },
              required: ['role', 'instructions']
            },
            description: 'Array of subagents to create'
          },
          execution_mode: {
            type: 'string',
            enum: ['parallel', 'sequential'],
            default: 'parallel',
            description: 'How to execute the subagents'
          },
          working_directory: {
            type: 'string',
            description: 'Working directory for the subagents (defaults to current directory)'
          }
        },
        required: ['task', 'agents']
      }
    },
  • Dispatch case in the CallToolRequestSchema handler that routes calls to the delegateToSubagents method.
    case 'delegate_to_subagents':
      return await this.delegateToSubagents(args);
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 mentions 'autonomous development' but doesn't explain what happens during delegation—whether subagents run independently, how errors are handled, if there are rate limits, or what permissions are required. For a tool that presumably creates and manages subprocesses, this lack of operational detail is a significant gap.

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 states the core purpose without redundancy. It's front-loaded with the main action and resource, and every word earns its place. No unnecessary elaboration or repetition exists.

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 delegating tasks to subagents, no annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns, how to monitor delegated tasks, or error handling. For a tool with 4 parameters and nested agent objects, more context is needed to guide effective use.

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%, so the schema fully documents all 4 parameters. The description adds no additional meaning beyond the schema's details about task, agents, execution mode, or working directory. It doesn't clarify parameter interactions or provide examples. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('delegate') and resource ('tasks to Goose CLI subagents') with a specific purpose ('for autonomous development'). It distinguishes from siblings like 'create_goose_recipe' or 'get_subagent_results' by focusing on task delegation rather than recipe creation or result retrieval. However, it could be more specific about what types of development tasks are appropriate.

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 'create_goose_recipe' for recipe management or 'get_subagent_results' for retrieving outcomes. There's no mention of prerequisites, typical use cases, or scenarios where delegation is preferred over direct execution. The agent must infer usage from the tool name 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

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