vcf-ops-mpb-mcp

Test, preview, verify and install

mpb_ship

Runs the full MPB pipeline for a design and halts at the first failing step, requiring confirm:true to install; otherwise it stops after verify.

Instructions

Runs the full MPB pipeline for a design and stops at the first failing step: source test (+ persist), collection preview, verify, install. Requires confirm: true to install; without it, it stops after verify.

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": {
      "designId": "<designId>"
    },
    "name": "mpb_ship"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Must be true to actually perform this destructive change
`designId`	Yes	MPB design UUID (see mpb_list_designs)
`logLevel`	No
`collectorId`	No
`credentials`	No
`skipSourceTest`	No	Skip when the source test already passed and was persisted

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 15, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the annotations, the description discloses important behavior: the pipeline order, first-failure stopping, source-test persistence, and that install only occurs with confirm=true while otherwise stopping after verify. It does not explain credential requirements, collector behavior, or other side effects of install.

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 two tightly written sentences, front-loaded with the main purpose and followed by the key confirm-gating behavior. There is no unnecessary wording.

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?

It covers the pipeline sequence and failure semantics well, which are central to this orchestration tool. Given the six parameters, nested credentials object, open-world hint, and no output schema, it is still somewhat incomplete because several parameters and install side effects are not explained.

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?

The description adds meaning for designId and confirm, especially the stop-after-verify behavior when confirm is absent. However, it leaves several parameters unexplained, including collectorId, credentials, and logLevel, and does not compensate for the 50% schema description coverage.

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 states a specific action and resource: it runs the full MPB pipeline for a design through source test, collection preview, verify, and install. It also distinguishes this orchestration behavior from the individual sibling steps by naming the pipeline stages.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for use: this is the end-to-end pipeline, and it stops at the first failing step. It also explains the confirm gate, but it does not explicitly say when to use this tool instead of the individual test/preview/verify/install siblings.

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