Skip to main content
Glama

fow_bootstrap

Destructive

Turn stakeholder scenarios into recorded lifecycle intent and a confirmed roadmap, then track correspondence, progress choices, and completion across a bootstrap cycle.

Instructions

Turn stakeholder scenarios into recorded lifecycle intent and an explicitly confirmed roadmap, then track correspondence, progress choices and completion of that bootstrap cycle. Route with operation: bind_implementation_provider, provider_binding_state, list_provider_bindings, start, resume, state, record_intake, record_contradiction, confirm_intake, derive_behavior, complete, cancel, guidance, record_answer, record_correspondence, roadmap, confirm_roadmap, record_continuation. Prerequisites: Select the real project/current bootstrap. Start from stakeholder scenarios and record only governing answers. Effects: Records intake, correspondence, confirmation and continuation; complete/cancel closes a cycle. Provider-binding replacement and optional behavior derivation are explicit operations. Never invent stakeholder approval or execute unclear scope. Exact help (replace operation_name with the selected route): fow_capabilities({"view":"operation","operation_tool":"fow_bootstrap","operation_name":"bind_implementation_provider"}).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoBootstrap workflow: import existing requirements, inspect existing code, create requirements or use guided engineering. Use a canonical path listed below. Applies to: start. Required by: start. Canonical values: requirements_import, code_import, requirements_creation, guided_engineering.
actorYesIdentity of the human or agent recording this action; retain the original identity when replaying its request.
answerNoStructured answer to the selected bootstrap or Oracle question; obtain its exact shape from operation help. Applies to: record_answer. Required by: record_answer. Exact required/optional dotted fields and guidance: fow_capabilities(view=operation, operation_tool=fow_bootstrap, operation_name=<selected route>).
intakeNoStructured bootstrap intake capturing scenario, constraints and existing-system context. Applies to: record_intake. Required by: record_intake. Exact required/optional dotted fields and guidance: fow_capabilities(view=operation, operation_tool=fow_bootstrap, operation_name=<selected route>).
reasonNoExplicit reason for the transition, cancellation or continuation action. Applies to: cancel, record_continuation. Required by: cancel, record_continuation.
surfacesNoExplicit provider evidence/association surfaces, such as repo; use the exact configured route contract. Applies to: bind_implementation_provider.
operationYesOperation selector for this multiplexer; use a canonical route listed below. Canonical values: bind_implementation_provider, provider_binding_state, list_provider_bindings, start, resume, state, record_intake, record_contradiction, confirm_intake, derive_behavior, complete, cancel, guidance, record_answer, record_correspondence, roadmap, confirm_roadmap, record_continuation.
project_idYesCanonical lifecycle project ID. Select the existing project explicitly; development Markdown authorities are separate from runtime projects.
request_idNoCaller-owned retry identity. For receipted mutations replay the same actor and contents; changed contents can conflict. Inspect exact operation help for its receipt policy.
bootstrap_idNoIdentifier of an existing bootstrap cycle; use the current cycle returned by guidance/state. Applies to: resume, state, record_intake, record_contradiction, confirm_intake, derive_behavior, complete, cancel, guidance, record_answer, record_correspondence, roadmap, confirm_roadmap, record_continuation. Required by: resume, state, record_intake, record_contradiction, confirm_intake, derive_behavior, complete, cancel, record_answer, record_correspondence, roadmap, confirm_roadmap, record_continuation.
project_nameNoExact registered project name associated with this bootstrap cycle. Applies to: start. Required by: start.
contradictionNoStructured bootstrap contradiction between the recorded intent and known authority, with the relevant references. Applies to: record_contradiction. Required by: record_contradiction. Exact required/optional dotted fields and guidance: fow_capabilities(view=operation, operation_tool=fow_bootstrap, operation_name=<selected route>).
milestone_idsNoExplicit existing milestone IDs in the roadmap or handover selection. Applies to: roadmap, confirm_roadmap. Required by: roadmap, confirm_roadmap.
provider_kindNoCanonical configured route category to bind/inspect: implementation_graph, bootstrap_behavior, packet_evidence, packet_execution or test_execution. Applies to: bind_implementation_provider, provider_binding_state. Required by: bind_implementation_provider, provider_binding_state.
correspondenceNoRecorded mapping from one current bootstrap answer revision to canonical requirements/goals/milestones and its disposition. Applies to: record_correspondence. Required by: record_correspondence. Exact required/optional dotted fields and guidance: fow_capabilities(view=operation, operation_tool=fow_bootstrap, operation_name=<selected route>).
progress_revisionNoIssued roadmap progress revision associated with the stakeholder's continuation choice. Applies to: record_continuation. Required by: record_continuation.
provider_scope_idNoAuthorized scope identity understood by the configured provider. Applies to: bind_implementation_provider. Required by: bind_implementation_provider.
replacement_reasonNoRequired explanation when replacing a different canonical host/provider association; replay of the same receipt does not replace it. Applies to: bind_implementation_provider.
continuation_choiceNoExplicit stakeholder continuation choice: continue the authorized roadmap or review the current result. Applies to: record_continuation. Required by: record_continuation. Canonical values: continue, review.
provider_context_idNoContext identity understood by an already configured optional provider route. Applies to: bind_implementation_provider.
roadmap_fingerprintNoFingerprint of the exact roadmap being confirmed or continued; stale intent/scope requires ordinary revision. Applies to: confirm_roadmap, record_continuation. Required by: confirm_roadmap, record_continuation.
completion_referenceNoReference to the actual evidence/authority supporting completion of this lifecycle object. Applies to: complete. Required by: complete.
confirmation_referenceNoReference to the stakeholder's actual confirmation of the recorded intent or roadmap. Applies to: confirm_intake, confirm_roadmap. Required by: confirm_intake, confirm_roadmap.
continuation_referenceNoReference to the actual stakeholder choice; do not synthesize approval from elapsed time. Applies to: record_continuation. Required by: record_continuation.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed27 schema fields changedv0.5.1
    • addedInput schema / properties / actor / description
      Added value: +"Identity of the human or agent recording this action; retain the original identity when replaying its request."
    • addedInput schema / properties / answer / description
      Added value: +"Structured answer to the selected bootstrap or Oracle question; obtain its exact shape from operation help. Applies to: record_answer. Required by: record_answer. Exact required/optional dotted fields and guidance: fow_capabilities(view=operation, operation_tool=fow_bootstrap, operation_name=<selected route>)."
    • addedInput schema / properties / answer / examples
      Added value: +[
      +  {
      +    "answer": "Return the integer successor through the declared API.",
      +    "answer_key": "successor-scenario",
      +    "kind": "intent",
      +    "question": "What should the software do?",
      +    "source_reference": "stakeholder:scenario-1"
      +  }
      +]
    • addedInput schema / properties / bootstrap_id / description
      Added value: +"Identifier of an existing bootstrap cycle; use the current cycle returned by guidance/state. Applies to: resume, state, record_intake, record_contradiction, confirm_intake, derive_behavior, complete, cancel, guidance, record_answer, record_correspondence, roadmap, confirm_roadmap, record_continuation. Required by: resume, state, record_intake, record_contradiction, confirm_intake, derive_behavior, complete, cancel, record_answer, record_correspondence, roadmap, confirm_roadmap, record_continuation."
    • addedInput schema / properties / completion_reference / description
      Added value: +"Reference to the actual evidence/authority supporting completion of this lifecycle object. Applies to: complete. Required by: complete."
    • addedInput schema / properties / confirmation_reference / description
      Added value: +"Reference to the stakeholder's actual confirmation of the recorded intent or roadmap. Applies to: confirm_intake, confirm_roadmap. Required by: confirm_intake, confirm_roadmap."
    • addedInput schema / properties / continuation_choice / description
      Added value: +"Explicit stakeholder continuation choice: continue the authorized roadmap or review the current result. Applies to: record_continuation. Required by: record_continuation. Canonical values: continue, review."
    • addedInput schema / properties / continuation_reference / description
      Added value: +"Reference to the actual stakeholder choice; do not synthesize approval from elapsed time. Applies to: record_continuation. Required by: record_continuation."
    • addedInput schema / properties / contradiction / description
      Added value: +"Structured bootstrap contradiction between the recorded intent and known authority, with the relevant references. Applies to: record_contradiction. Required by: record_contradiction. Exact required/optional dotted fields and guidance: fow_capabilities(view=operation, operation_tool=fow_bootstrap, operation_name=<selected route>)."
    • addedInput schema / properties / correspondence / description
      Added value: +"Recorded mapping from one current bootstrap answer revision to canonical requirements/goals/milestones and its disposition. Applies to: record_correspondence. Required by: record_correspondence. Exact required/optional dotted fields and guidance: fow_capabilities(view=operation, operation_tool=fow_bootstrap, operation_name=<selected route>)."
    • addedInput schema / properties / correspondence / examples
      Added value: +[
      +  {
      +    "answer_key": "successor-scenario",
      +    "answer_revision": 1,
      +    "canonical_references": {
      +      "goal_node_ids": [],
      +      "milestone_ids": [],
      +      "requirement_ids": [
      +        "current-requirement-id"
      +      ]
      +    },
      +    "disposition": "consistent",
      +    "rationale": "The current canonical requirement expresses the recorded scenario."
      +  }
      +]
    • addedInput schema / properties / intake / description
      Added value: +"Structured bootstrap intake capturing scenario, constraints and existing-system context. Applies to: record_intake. Required by: record_intake. Exact required/optional dotted fields and guidance: fow_capabilities(view=operation, operation_tool=fow_bootstrap, operation_name=<selected route>)."
    • addedInput schema / properties / milestone_ids / description
      Added value: +"Explicit existing milestone IDs in the roadmap or handover selection. Applies to: roadmap, confirm_roadmap. Required by: roadmap, confirm_roadmap."
    • addedInput schema / properties / operation / description
      Added value: +"Operation selector for this multiplexer; use a canonical route listed below. Canonical values: bind_implementation_provider, provider_binding_state, list_provider_bindings, start, resume, state, record_intake, record_contradiction, confirm_intake, derive_behavior, complete, cancel, guidance, record_answer, record_correspondence, roadmap, confirm_roadmap, record_continuation."
    • addedInput schema / properties / operation / examples
      Added value: +[
      +  "bind_implementation_provider"
      +]
    • addedInput schema / properties / path / description
      Added value: +"Bootstrap workflow: import existing requirements, inspect existing code, create requirements or use guided engineering. Use a canonical path listed below. Applies to: start. Required by: start. Canonical values: requirements_import, code_import, requirements_creation, guided_engineering."
    • addedInput schema / properties / progress_revision / description
      Added value: +"Issued roadmap progress revision associated with the stakeholder's continuation choice. Applies to: record_continuation. Required by: record_continuation."
    • addedInput schema / properties / project_id / description
      Added value: +"Canonical lifecycle project ID. Select the existing project explicitly; development Markdown authorities are separate from runtime projects."
    • addedInput schema / properties / project_name / description
      Added value: +"Exact registered project name associated with this bootstrap cycle. Applies to: start. Required by: start."
    • addedInput schema / properties / provider_context_id / description
      Added value: +"Context identity understood by an already configured optional provider route. Applies to: bind_implementation_provider."
    • addedInput schema / properties / provider_kind / description
      Added value: +"Canonical configured route category to bind/inspect: implementation_graph, bootstrap_behavior, packet_evidence, packet_execution or test_execution. Applies to: bind_implementation_provider, provider_binding_state. Required by: bind_implementation_provider, provider_binding_state."
    • addedInput schema / properties / provider_scope_id / description
      Added value: +"Authorized scope identity understood by the configured provider. Applies to: bind_implementation_provider. Required by: bind_implementation_provider."
    • addedInput schema / properties / reason / description
      Added value: +"Explicit reason for the transition, cancellation or continuation action. Applies to: cancel, record_continuation. Required by: cancel, record_continuation."
    • addedInput schema / properties / replacement_reason / description
      Added value: +"Required explanation when replacing a different canonical host/provider association; replay of the same receipt does not replace it. Applies to: bind_implementation_provider."
    • addedInput schema / properties / request_id / description
      Added value: +"Caller-owned retry identity. For receipted mutations replay the same actor and contents; changed contents can conflict. Inspect exact operation help for its receipt policy."
    • addedInput schema / properties / roadmap_fingerprint / description
      Added value: +"Fingerprint of the exact roadmap being confirmed or continued; stale intent/scope requires ordinary revision. Applies to: confirm_roadmap, record_continuation. Required by: confirm_roadmap, record_continuation."
    • addedInput schema / properties / surfaces / description
      Added value: +"Explicit provider evidence/association surfaces, such as repo; use the exact configured route contract. Applies to: bind_implementation_provider."
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With destructiveHint=true and openWorldHint=true already in annotations, the description still adds substantive behavior: it says what gets recorded (intake, correspondence, confirmation, continuation), that complete/cancel closes a cycle, that provider-binding replacement and behavior derivation are explicit opt-in operations, and that approval must never be invented. The one gap is that individual operation-level side effects and the confirmation receipt semantics are deferred to the capabilities lookup.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the Prerequisites/Effects blocks are well-structured, so the skeleton is good. But the description re-lists all 19 operation names that are already enumerated in the `operation` schema enum, which is pure duplication and dominates the token budget. The final fow_capabilities pointer is verbose but earns its place.

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 24-parameter, 19-route multiplexer with an output schema available (so return values need no explanation), the description covers purpose, prerequisites, effects, and the escape hatch for exact per-operation contracts. The residual gap is that the object-typed payloads (intake, contradiction, correspondence, answer) are only reachable via an extra fow_capabilities call, so an agent cannot invoke those routes from this definition alone.

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 baseline is 3 and the per-property 'Applies to / Required by' notes already tell the agent which operation consumes which field. The description itself contributes no parameter meaning beyond the operation-route list, which is duplicated in the schema's canonical values. It correctly defers the nested payload shapes to operation help rather than pretending to document them.

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 first sentence names a specific transformation (stakeholder scenarios -> recorded lifecycle intent + explicitly confirmed roadmap) plus the ongoing tracking function, which is far more than a restatement of the name. It is distinguishably a lifecycle-bootstrap multiplexer rather than a sibling like fow_handover or fow_packet_advance. It loses a point only because the phrasing is dense internal jargon that an outside agent must decode.

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?

Prerequisites ('Select the real project/current bootstrap. Start from stakeholder scenarios and record only governing answers.') give real context for when this tool is the right entry point, and the enumerated operation routes imply the sub-workflow. However, there is no explicit when-not-to-use guidance and no routing against the 35 sibling tools (e.g. when to bootstrap vs. fow_goal or fow_campaign_author), so usage is only partially disambiguated.

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