Skip to main content
Glama
Secret-art-stack

spillway-mcp

by Secret-art-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

agy_spawn_swarm

Read-onlyIdempotent

Dispatches multiple read-only subagents across non-overlapping directory partitions to explore independent subsystems in one turn, returning an aggregated markdown report.

Instructions

Dispatch multiple read-only Antigravity subagents using gemini-3.8-flash-low or gemini-3.8-flash-medium across strictly disjoint directory partitions. WHEN TO USE: Exploring multiple independent subsystems or directories in a single turn. DO NOT USE FOR: Single-directory research (use agy_delegate_research), single-file signature extraction (use local_file_scout), or overlapping directory paths (rejected by partition validator). RETURNS: Aggregated markdown report per subagent task plus telemetry footer.

Input Schema

NameRequiredDescriptionDefault
cwdNoOptional workspace root directory path.
tasksYesArray of subagent tasks with strictly non-overlapping directory globs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv1.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / cwd / description
      Previous value: -"Optional workspace root directory."New value: +"Optional workspace root directory path."
    • changedInput schema / properties / tasks / description
      Previous value: -"Array of parallel subagent tasks with disjoint path partitions."New value: +"Array of subagent tasks with strictly non-overlapping directory globs."
    • addedInput schema / properties / tasks / items / additionalProperties
      Added value: +false
    • changedInput schema / properties / tasks / items / properties / id / description
      Previous value: -"Unique task identifier."New value: +"Unique task identifier (e.g. \"auth-worker\")."
    • addedInput schema / properties / tasks / items / properties / id / minLength
      Added value: +1
    • addedInput schema / properties / tasks / items / properties / paths / minItems
      Added value: +1
    • changedInput schema / properties / tasks / items / properties / prompt / description
      Previous value: -"Task instructions for this subagent."New value: +"Read-only research instructions for this subagent partition."
    • addedInput schema / properties / tasks / items / properties / prompt / minLength
      Added value: +1
    • addedInput schema / properties / tasks / items / properties / tier / default
      Added value: +"flash-low"
    • changedInput schema / properties / tasks / items / properties / tier / description
      Previous value: -"Swarm tier (defaults to flash-low)."New value: +"Swarm model tier (defaults to flash-low)."
    • addedInput schema / properties / tasks / minItems
      Added value: +1
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is carried. The description still adds value beyond that: the disjoint-partition validator will reject overlaps, subagents are read-only, the model tiers used, and the return shape (aggregated markdown plus telemetry footer) which matters because there is no output schema. It does not quantify limits such as max task count or failure handling.

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?

A single dense paragraph with front-loaded purpose followed by labelled WHEN TO USE, DO NOT USE FOR, and RETURNS clauses. Every sentence carries an actionable constraint; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema and 100% schema coverage, the description covers purpose, exclusions, partitioning constraint, and return shape. The one ambiguity left is when to prefer the flash-medium tier over the default flash-low, which the description names but does not differentiate.

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 both the cwd and the nested task fields (id, tier, paths, prompt) are already documented with examples and constraints. The description only restates the disjoint-path rule and the tier names; it adds no format or syntax detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource (dispatch read-only subagents) plus the defining constraint: strictly disjoint directory partitions and specified model tiers. This is immediately distinguishable from agy_delegate_research and local_file_scout, which the description names as alternatives.

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

Usage Guidelines5/5

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

Explicit WHEN TO USE (multiple independent subsystems/directories in one turn) and DO NOT USE FOR with the exact sibling to use instead for each excluded case, including that overlapping paths are rejected by the validator. Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools