Flower MCP

Overview Schema Source Related Servers Discussions Admin

fow_promote_milestone

Plan a milestone by defining its scope from requirements, dependency closure, and entry/exit/risk policies. This does not accept results.

Instructions

Create planned milestone scope from canonical requirements, dependencies and entry/exit/risk policies. Actual result acceptance uses fow_accept_milestone. Single operation; call directly without an operation argument. Prerequisites: Supply canonical requirements, dependency closure and planning entry/exit/risk policies. Effects: Records planned milestone scope. Nonempty acceptance_evidence is rejected; promotion does not accept the result. Exact help (replace operation_name with the selected route): fow_capabilities({"view":"operation","operation_tool":"fow_promote_milestone","operation_name":"call"}).

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": {
      "project_id": "<project_id>",
      "name": "<name>",
      "requirement_ids": "<requirement_ids>",
      "dependency_closure_ids": "<dependency_closure_ids>",
      "entry_policy": "<entry_policy>",
      "exit_policy": "<exit_policy>",
      "risk_disposition": "<risk_disposition>",
      "actor": "<actor>"
    },
    "name": "fow_promote_milestone"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Human-readable project or milestone name.
`actor`	Yes	Identity of the human or agent recording this action; retain the original identity when replaying its request.
`project_id`	Yes	Canonical lifecycle project ID. Select the existing project explicitly; development Markdown authorities are separate from runtime projects.
`request_id`	No	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.
`exit_policy`	Yes	Declared exit/acceptance conditions for the milestone's planned scope.
`entry_policy`	Yes	Declared entry conditions for the milestone's planned scope.
`requirement_ids`	Yes	Explicit existing requirement IDs defining the selected scope.
`risk_disposition`	Yes	Declared treatment of milestone planning risks.
`acceptance_evidence`	No	Reserved compatibility input; milestone promotion plans scope and rejects nonempty acceptance evidence. Use fow_accept_milestone for actual governed acceptance.
`dependency_closure_ids`	Yes	Requirement IDs included in the milestone's explicit dependency closure.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.5.1Oct 16, 2026

addedInput schema / properties / acceptance_evidence / description

Added value: +"Reserved compatibility input; milestone promotion plans scope and rejects nonempty acceptance evidence. Use fow_accept_milestone for actual governed acceptance."

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 / dependency_closure_ids / description

Added value: +"Requirement IDs included in the milestone's explicit dependency closure."

addedInput schema / properties / entry_policy / description

Added value: +"Declared entry conditions for the milestone's planned scope."

addedInput schema / properties / exit_policy / description

Added value: +"Declared exit/acceptance conditions for the milestone's planned scope."

addedInput schema / properties / name / description

Added value: +"Human-readable project or milestone name."

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 / 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 / requirement_ids / description

Added value: +"Explicit existing requirement IDs defining the selected scope."

addedInput schema / properties / risk_disposition / description

Added value: +"Declared treatment of milestone planning risks."

First observedv0.1.0Oct 16, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false; the description goes further by disclosing the observable effect ('Records planned milestone scope') and a hard failure condition (nonempty acceptance_evidence is rejected). It does not discuss retry/idempotency behavior despite idempotentHint=false, though the request_id parameter description in the schema partly covers that.

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?

Front-loaded with purpose and the alternative route, then labeled Prerequisites/Effects lines that scan quickly. The trailing 'Exact help' boilerplate with the operation_name substitution instruction is lower-value and slightly bloats an otherwise tight definition.

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 10-parameter governed mutation with an output schema, the description covers purpose, prerequisites, effect, rejection rule, and the sibling alternative, so an agent has enough to invoke it correctly. Minor gaps remain around failure/retry semantics, which the request_id schema description only partly addresses.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds genuine meaning beyond the schema for the two highest-risk inputs: acceptance_evidence is a 'reserved compatibility input' that must stay empty, and the requirement/dependency/policy inputs are framed as prerequisites the caller must supply. That is useful routing information, though no syntax or format detail is added.

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 ('Create planned milestone scope') and immediately names the contrasting sibling ('Actual result acceptance uses fow_accept_milestone'), so the agent can separate scope planning from acceptance without opening either schema. The scope is further bounded by the inputs it draws from (requirements, dependencies, entry/exit/risk policies).

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 explicit when-to-use ('Create planned milestone scope...'), when-not (rejects nonempty acceptance_evidence; promotion does not accept the result), and the alternative route (fow_accept_milestone). It also answers the invocation-shape question directly: 'Single operation; call directly without an operation argument.'

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