Skip to main content
Glama

Bootstrap Project

bootstrap_project

Generates PRD, milestone, active-task, and config templates to onboard an unknown repository, creating the files and directories needed to start project tracking.

Instructions

Auto-generate template files and directories (PRD, milestones, active tasks, config yaml) to instantly onboard an unknown repository.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bootstrap_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose that files and directories are created and names the artifact types, but says nothing about whether existing files are overwritten, whether the operation is idempotent, what permissions or preconditions are required, or how to recover from a partial run — significant gaps for a filesystem-mutating tool.

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?

A single well-formed sentence that front-loads the action and then lists the produced artifacts, with no filler. It is efficient, though the parenthetical artifact list is dense enough that a clause about the target path would have been worth the space.

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?

An output schema exists, so return values need not be described, which lowers the bar. Still, for a bootstrap/scaffolding mutation with zero annotation coverage and an undocumented path parameter, an agent is left without the overwrite-safety and targeting information needed to invoke it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter ('path', defaulting to '.') with 0% schema description coverage, and the description never mentions it. With coverage this low the description is expected to compensate by explaining that the path is the target repository root, but it instead adds no parameter meaning whatsoever.

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 gives a specific verb ('auto-generate') and resource ('template files and directories') and enumerates the concrete artifacts produced (PRD, milestones, active tasks, config yaml). It is clear what the tool does, though it never explicitly contrasts itself with near-siblings such as adopt_existing_project, init_context, or create_project_workspace.

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 phrase 'to instantly onboard an unknown repository' implies the triggering situation (a repo with no existing scaffolding), which is genuinely useful context. However, it gives no explicit when-not guidance and does not route the agent away from similarly scoped siblings like adopt_existing_project or init_context, so the selection logic 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.