Skip to main content
Glama
Peter-N91

hve-squad MCP server

by Peter-N91
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Squad Run

squad_run

Runs the full squad pipeline for any request: classifies, dispatches roles through Research, Plan, Implement, Review with gates, and returns a host-driven dispatch request.

Instructions

Run the full squad pipeline for any request. Hands the request to the Squad Coordinator, which classifies it against the routing table and dispatches the matched roles through Research -> Plan -> Implement -> Review, carrying the council Implementation Gate, the autopilot/autonomous Human Gates, and the notification approval contract unchanged. This is the catch-all entry point and runs at the confirm tier with gates. Set mode=autonomous for the bounded validator loop or mode=autopilot for the full gated pipeline. Delegated execution: returns the Coordinator persona, matched routing, and a framed dispatch request for the host to drive. Use when no narrower squad_* tool fits, or for end-to-end work.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoOptional autonomy mode: autonomous (bounded validator loop) or autopilot (full gated pipeline).
tierNoOptional model-tier hint overriding the coordinator's cost-first default.
ownerNoOptional Member Name from team.md to pick a specific named member.
squadNoOptional federation sub-squad to target (state under .copilot-tracking/squad/members/<name>/); omit outside a federation.
contextNoOptional free-form context to frame the pipeline.
profileNoOptional squad profile to seed when the project has no squad yet.
requestYesThe work for the squad this turn (any intent; the Coordinator classifies it).
routingNoOptional per-role model routing mode, persisted in team.md until changed: ranked (pick each role's model by fit from the squad model catalog), manual (ask you to choose each role's model from the models this host can run), or off (no Model column; dispatch with no model parameter). Omit to keep the recorded mode. Ignored on an unattended run.
discoveryNoOptional discovery-gate depth for a request that states a goal with no requirement artifact behind it: quick (analyst), standard (designer then analyst), deep (designer, then challenger and experimenter, then analyst), or skip. An explicit depth beats the coordinator's one-time offer. Ignored on an unattended run, which has nobody for the gate to interview.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • addedInput schema / properties / routing
      Added value: +{
+  "description": "Optional per-role model routing mode, persisted in team.md until changed: ranked (pick each role's model by fit from the squad model catalog), manual (ask you to choose each role's model from the models this host can run), or off (no Model column; dispatch with no model parameter). Omit to keep the recorded mode. Ignored on an unattended run.",
+  "enum": [
+    "off",
+    "ranked",
+    "manual"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changedv0.6.3
    • addedInput schema / properties / discovery
      Added value: +{
+  "description": "Optional discovery-gate depth for a request that states a goal with no requirement artifact behind it: quick (analyst), standard (designer then analyst), deep (designer, then challenger and experimenter, then analyst), or skip. An explicit depth beats the coordinator's one-time offer. Ignored on an unattended run, which has nobody for the gate to interview.",
+  "enum": [
+    "quick",
+    "standard",
+    "deep",
+    "skip"
+  ],
+  "type": "string"
+}
  3. Changed1 schema field changedv0.2.1
    • addedInput schema / properties / squad
      Added value: +{
+  "description": "Optional federation sub-squad to target (state under .copilot-tracking/squad/members/<name>/); omit outside a federation.",
+  "pattern": "^[a-z0-9][a-z0-9-]*$",
+  "type": "string"
+}
  4. First observedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it describes the pipeline stages, gates, confirm tier, mode behaviors, and delegated execution return value. It also discloses the notification approval contract, which is a meaningful operational constraint.

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?

Front-loads the core purpose, then layers pipeline mechanics, mode guidance, delegation behavior, and usage routing in a logical order. Despite being dense, every sentence adds operational context appropriate for a complex catch-all tool with no annotations.

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

Completeness5/5

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

Given 9 parameters, no annotations, and no output schema, the description is complete enough for an agent to understand the tool's scope, behavior, and return shape. Parameter details are left to the fully populated schema, which is appropriate.

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 already documents all 9 parameters. The description adds some mode semantics but nothing beyond the schema for most parameters; its mention of a 'confirm tier' even risks confusion against the schema's tier enum of fast/default.

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+resource ('Run the full squad pipeline for any request') and positions itself as the catch-all entry point. It explicitly distinguishes itself from siblings by saying to use narrower squad_* tools when they fit, so an agent can route without opening schemas.

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?

Gives an explicit when-to-use condition ('when no narrower squad_* tool fits, or for end-to-end work') and names the alternative class of tools. It also explains mode-specific behavior, so the agent knows when to select this tool and how to configure it.

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