aibvf-mcp

sequence_portfolio

Read-onlyIdempotent

Turn a scored AI portfolio into three waves with gates over a configurable horizon, so the roadmap respects the change capacity of each business function. CALL THIS after score_portfolio when the user asks what to stop, fund first, defer or fit into the next 90 days. It does not change any verdict or re-score the business case. Stops enter wave 1 to reclaim budget and attention, quicker Accelerates enter wave 2, complex Accelerates and Fixes enter wave 3 behind their re-score gates. Pass the portfolio returned by score_portfolio directly through portfolio, or pass organization plus initiatives; both score shapes are accepted and nested values are flattened. readiness sets capture rates and pacing, max_parallel_per_function caps simultaneous change in one function per wave, and horizon_days divides the plan into three equal windows. Capacity overflow is reported as a conflict or a deferral beyond the horizon, never hidden. Run recommend_improvements for a Fix before treating its wave placement as permission to proceed. Pure deterministic calculation, no network, auth, or side effects.

Input Schema

TableJSON Schema

Name	Required	Description
`portfolio`	No	Alternative input: the same AI BVF v1.0 portfolio document score_portfolio accepts (organization + initiatives with nested {value} pillar scores). Pass either this OR the top-level organization + initiatives; nested score values are flattened automatically, and missing pillars are estimated honestly.
`readiness`	Yes	Organisational readiness applied across the portfolio; sets capture rates and pacing. Measure it with infer_readiness when process numbers exist.
`constraints`	No	Change-capacity constraints. The defaults encode the core principle: no function absorbs unlimited concurrent change.
`initiatives`	No	The portfolio to sequence. Each initiative carries flat 0-100 pillar numbers (not the nested value objects of the portfolio wire format).
`organization`	No	Organisation context used when initiatives are passed at the top level. Required with top-level initiatives and ignored when portfolio is supplied.

Output Schema

TableJSON Schema

Name	Required	Description
`audit`	Yes	Reproducibility record: engine version, the rules that fired, and the resolved inputs. Deterministic, no timestamps. If the verdict is challenged months later, the same inputs on the same engine version reproduce it exactly.
`waves`	Yes	Three waves with named gates: Stops first (free the budget), quick Accelerates second (buy trust), complex Accelerates plus Fixes third (spend the trust). Present this to the user as the rollout plan.
`totals`	Yes	Counts: stopped, quick_wins, complex_or_fix, deferred.
`skipped`	No
`bvf_version`	Yes
`capacity_conflicts`	Yes	Where more initiatives land on one function than it can absorb per wave, with the deferral applied. Surface these: an overloaded function is how good portfolios fail.
`sequencing_principles`	Yes
`deferred_beyond_horizon`	No	Initiatives that did not fit the horizon under the capacity constraint; they need their own decision.
`aggregate_accelerate_value_eur`	No	Sum of modelled net EUR for the sequenced Accelerates, low and high.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedAug 23, 2026

addedInput schema / description

Added value: +"Sequence one scored portfolio by passing either portfolio, or organization plus initiatives, never both. readiness is always required because it sets pacing. constraints are optional and default to two concurrent initiatives per function across a 90-day horizon."

addedInput schema / properties / initiatives / items / properties / ai_tier / description

Added value: +"AI ambition, gen1, gen2 or gen3. Higher tiers are treated as more complex when wave placement is decided."

addedInput schema / properties / initiatives / items / properties / function / description

Added value: +"Business function absorbing the change. Capacity limits are enforced against this field."

addedInput schema / properties / initiatives / items / properties / id / description

Added value: +"Stable initiative identifier used in waves, conflicts and deferrals."

addedInput schema / properties / initiatives / items / properties / name / description
```
Added value: +"Initiative name shown in the sequenced plan."
```

addedInput schema / properties / initiatives / items / properties / scores / description

Added value: +"The four flat 0-100 pillar values used to classify and place the initiative. Pass the score_initiative scores_used values, not nested score objects."

addedInput schema / properties / initiatives / items / properties / scores / properties / change_enablement / description
```
Added value: +"Change-enablement score from score_initiative, 0-100."
```
addedInput schema / properties / initiatives / items / properties / scores / properties / financial_return / description
```
Added value: +"Financial-return score from score_initiative, 0-100."
```
addedInput schema / properties / initiatives / items / properties / scores / properties / governance_risk / description
```
Added value: +"Governance-risk score from score_initiative, 0-100, where higher means more risk."
```
addedInput schema / properties / initiatives / items / properties / scores / properties / strategic_alignment / description
```
Added value: +"Strategic-alignment score from score_initiative, 0-100."
```

addedInput schema / properties / organization / description

Added value: +"Organisation context used when initiatives are passed at the top level. Required with top-level initiatives and ignored when portfolio is supplied."

Changed3 schema fields changedJul 5, 2026

addedInput schema / properties / portfolio

Added value: +{
+  "description": "Alternative input: the same AI BVF v1.0 portfolio document score_portfolio accepts (organization + initiatives with nested {value} pillar scores). Pass either this OR the top-level organization + initiatives; nested score values are flattened automatically, and missing pillars are estimated honestly.",
+  "type": "object"
+}

changedInput schema / required

Previous value: -[
-  "organization",
-  "initiatives",
-  "readiness"
-]New value: +[
+  "readiness"
+]

changedOutput schema / properties / waves / items / properties / gate_to_next / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

AddedJul 5, 2026

TDQS

A5/5.0

Behavior5/5

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

The description adds meaningful behavioral context beyond the annotations: it explicitly states the tool is a pure deterministic calculation with no network, auth, or side effects, and that capacity overflow is never hidden but reported as a conflict or deferral. It also clarifies it does not mutate or re-score anything. Nothing contradicts the readOnly, idempotent, or destructive annotations.

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?

The description is dense but each sentence earns its place. It front-loads the critical call placement ('CALL THIS after score_portfolio'), gives the essential scope, then covers inputs and behavior without repetition or filler.

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?

For a complex tool with nested inputs and five parameters, the description covers required input types, valid alternative input shapes, constraint behavior, overflow semantics, and integration with recommend_improvements. An output schema exists, so return-value details are not needed in the description. The context is complete enough for an agent to invoke it correctly without ambiguity.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds high-level semantic guidance that the schema alone doesn't provide: pass the output of score_portfolio directly into portfolio, or use organization plus initiatives; readiness sets capture rates and pacing; horizon_days splits the plan into three equal windows; and max_parallel_per_function caps simultaneous change per function per wave. This helps the agent make correct invocation decisions quickly.

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?

The description opens with a specific verb and resource—turn a scored AI portfolio into three waves with gates over a configurable horizon—and clearly states what it does not do: it does not change verdicts or re-score the business case. It also distinguishes itself from score_portfolio and recommend_improvements by positioning the tool's role in the workflow.

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?

The description explicitly says 'CALL THIS after score_portfolio when the user asks what to stop, fund first, defer or fit into the next 90 days.' It also names recommend_improvements as a required prerequisite for Fix initiatives before wave placement is treated as permission to proceed, so the agent receives concrete when-to-use and when-not-to-proceed guidance.

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

All aibvf-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.