Skip to main content
Glama

start_competitive_planning

Launches two planning workers to create competing implementation plans for a complex feature, so teams can compare approaches before coding.

Instructions

Start competitive planning for a complex feature. Spawns two workers in planning mode to create competing implementation plans.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectDir": "<projectDir>",
      "featureId": "<featureId>"
    },
    "name": "start_competitive_planning"
  }
}

Input Schema

NameRequiredDescriptionDefault
featureIdYesID of the feature to plan
projectDirYesAbsolute path to the project directory
customPromptANoCustom prompt for planner A
customPromptBNoCustom prompt for planner B
forceCompetitiveNoForce competitive planning even if not detected as complex

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose real behavior beyond the name — two concurrent workers in planning mode producing competing plans — but says nothing about whether the call blocks or returns immediately, what handles/IDs come back, cost or concurrency implications, or what prerequisites (feature already registered) must hold.

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?

Two tight sentences with the action first and the mechanism second; no filler, no repetition of the title, nothing that could be removed without losing information.

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

Completeness3/5

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

With no annotations and no output schema, the description must cover side effects and results, and it stops short: an agent still cannot tell what is returned from the spawn, how to monitor the two workers, or whether planning must be followed by evaluation or approval steps.

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 all five parameters including customPromptA/B and forceCompetitive are already documented in the schema. The description adds nothing about how the custom prompts alter the competing-plan setup or how forceCompetitive interacts with the "complex feature" condition, so baseline 3 applies.

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?

Names a specific verb+resource ("Start competitive planning") and adds the concrete mechanism: spawning two workers in planning mode to produce competing plans. That distinguishes the outcome from a generic worker spawn, though it never names which sibling (start_parallel_workers, start_worker) it replaces.

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?

"For a complex feature" implies a usage condition, and the schema's forceCompetitive hints at an override path, but the description gives no explicit when-not guidance, no alternative tool for simple features, and no stated next step such as evaluating the resulting plans.

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