Skip to main content
Glama
Platano78

Smart-AI-Bridge

spawn_subagent

Create subagents with predefined roles for code review, security auditing, planning, refactoring, test generation, or documentation. Each role has customized prompts and tools for specific tasks.

Instructions

Spawn specialized AI subagent - Create subagents with predefined roles (code-reviewer, security-auditor, planner, refactor-specialist, test-generator, documentation-writer). Each role has customized prompts, tools, and behavior for specific tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleYesSubagent role: code-reviewer (quality review), security-auditor (vulnerability detection), planner (task breakdown), refactor-specialist (code improvement), test-generator (test creation), documentation-writer (docs generation), tdd-decomposer (break task into TDD subtasks), tdd-test-writer (RED phase), tdd-implementer (GREEN phase), tdd-quality-reviewer (quality gate)
taskYesTask description for the subagent to perform
file_patternsNoOptional glob patterns for files to analyze (e.g., ["src/**/*.js", "*.test.ts"])
contextNoAdditional context object for the subagent
verdict_modeNoVerdict parsing mode: summary (extract key fields only) or full (return complete verdict data)summary
write_filesNoWrite generated code blocks to files (default: false). Set to true to save output code to work_directory.
work_directoryNoDirectory for generated files (default: /tmp/subagent-{role}-{timestamp})
Behavior2/5

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

No annotations are provided, and the description only mentions subagents have 'customized prompts, tools, and behavior' without detailing side effects (e.g., file writing if write_files=true), resource consumption, error handling, or how results are returned.

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 two sentences with no wasted words: first sentence states purpose, second enumerates roles. It is front-loaded and efficient.

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?

Despite 7 parameters and no output schema, the description omits crucial details about subagent behavior, execution model (synchronous/asynchronous), return format, and usage of context object. For a complex tool, this is insufficient.

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 baseline is 3. The description adds value by summarizing roles and purposes, which complements the schema's enum descriptions, but does not significantly deepen understanding of other parameters like task, context, or work_directory.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (spawn subagent) and the resource (specialized AI subagent), listing specific roles and their purposes, distinguishing it from sibling tools like analyze_file or council.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by describing roles and tasks, but does not explicitly guide when to use this tool vs alternatives like council or parallel_agents, nor does it mention when not to use it.

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/Platano78/Smart-AI-Bridge'

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