Skip to main content
Glama

spawn_agent

Launch specialized autonomous agents for development tasks. Each agent is configured with role-specific instructions, full tool access, and dependency management, operating within a given repository.

Instructions

Spawn fully autonomous Claude agent with complete tool access

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentTypeYesType of specialized agent to spawn (e.g., "backend", "frontend", "testing", "documentation", "devops", "researcher"). This determines the agent's role-specific instructions and capabilities.
repositoryPathYesAbsolute path to the repository where the agent will operate. This is the working directory for all agent operations.
taskDescriptionYesDetailed description of the specific task or responsibility this agent should handle. Should be clear, actionable, and include any important context or requirements.
capabilitiesNoArray of capabilities or tools the agent should have access to. Defaults to "ALL_TOOLS" which grants full access to all available tools including file operations, code analysis, web browsing, and coordination tools.
dependsOnNoArray of agent IDs that this agent depends on. The agent will only be spawned after all dependencies are satisfied (agents exist and are active/completed).
metadataNoOptional metadata object for storing additional agent configuration, context, or coordination information.
autoCreateRoomNoWhether to automatically create a coordination room for this agent. If not specified, uses the default behavior for the agent type (most agent types auto-create rooms by default).
roomIdNoOptional existing room ID to assign the agent to. If provided, the agent will join this room instead of creating a new one.
Behavior2/5

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

With no annotations, the description carries the full burden. It claims 'fully autonomous' and 'complete tool access' but fails to disclose important behaviors such as resource consumption, background execution, coordination room creation (implied by autoCreateRoom), or lifecycle management.

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 very concise (7 words) and front-loaded with the core action. However, for an 8-parameter tool, more structured detail could be beneficial without being verbose.

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 (8 parameters, no output schema) and many sibling tools, the description is insufficient. It lacks explanation of return value, agent lifecycle, coordination room usage, and how spawned agents interact with other tools.

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 coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the already detailed parameter descriptions in the input schema. For example, it doesn't clarify how agentType affects behavior beyond the schema.

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 'spawn' and the resource 'fully autonomous Claude agent with complete tool access'. It distinguishes the tool from siblings like terminate_agent or list_agents, though it doesn't explicitly differentiate its purpose.

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 (e.g., create_task, orchestrate_objective). The description does not mention when not to use it or any prerequisites.

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/ZachHandley/ZMCPTools'

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