vcf-ops-mpb-mcp

Verify design from preview

mpb_verify_design

Marks an MPB design as verified using a collection preview job, defaulting to the latest, to unlock installation.

Instructions

Marks the design verified using a collection preview job (default: the latest one). Required before install.

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_verify_design"
  }
}

Input Schema

Name	Required	Description	Default
`jobId`	No
`designId`	Yes	MPB design UUID (see mpb_list_designs)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 15, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, open-world mutation, and the description usefully adds the verification state change and its dependency on a prior preview job. It does not disclose whether the operation is idempotent, what happens if the referenced preview job is stale or missing, or what a successful call returns.

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?

Two short sentences, zero filler, with the action front-loaded and the defaulting rule and prerequisite following immediately. Every clause carries information an agent needs.

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 two-parameter mutation with annotations supplied and no output schema, the description covers the action, the ordering constraint, and the optional-parameter default. The one remaining gap is error/edge behavior when no preview job exists, which is minor at this complexity level.

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 only 50% — designId is documented inline, but jobId has no schema description. The description compensates well by explaining that jobId identifies a collection preview job and that omitting it uses the latest, which is exactly the missing meaning. It does not clarify how to obtain a valid jobId, keeping it below 5.

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?

States a specific verb and resource ('marks the design verified') plus the mechanism ('using a collection preview job'), which cleanly separates it from siblings like mpb_collection_preview (which produces the job) and mpb_install (which consumes the verification). It stops short of naming any sibling explicitly, but the action is unambiguous.

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?

'Required before install' gives a concrete prerequisite ordering that an agent can act on, and '(default: the latest one)' signals jobId is optional. It does not state failure conditions or when NOT to call it, so it falls just short of full when/when-not guidance.

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