vcf-ops-mpb-mcp

Update design name/description/version

mpb_update_design_info

Updates a design’s name, description, and version. Bump the version before each reinstall so the adapter can flag the install as OUT_OF_DATE.

Instructions

Updates design info. Bump version before every reinstall: it flows to the adapter and drives the OUT_OF_DATE install status.

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

Input Schema

Name	Required	Description
`name`	No
`version`	No
`designId`	Yes	MPB design UUID (see mpb_list_designs)
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 15, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so safety is partly covered. The description adds genuinely non-obvious behavior: the version value flows to the adapter and drives the OUT_OF_DATE install status. However, it omits mutation semantics that matter for a partial update, such as whether unsupplied fields are left untouched.

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?

Two tight sentences with the operational warning front-loaded and no filler. The opening "Updates design info" is close to a restatement of the name, but it works as a lead-in rather than padding.

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?

For a 4-parameter mutation tool with 25% schema coverage and no output schema, the description covers version but leaves name/description semantics and the update-merge behavior unexplained. It is adequate but has clear gaps an agent would want filled.

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 coverage is only 25% (only designId is described), so the description must compensate. It does explain version's role well, but name and description get no semantic treatment at all, leaving half the parameters undocumented in both schema and prose.

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?

"Updates design info" names a specific verb and resource, and the title disambiguates the fields to name/description/version. It is clearly distinct from siblings like mpb_create_design, mpb_delete_designs, and the read-only mpb_get_design, though the body sentence itself never enumerates which fields are updatable.

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?

It gives one concrete when-rule (bump version before every reinstall) but no overall when-to-use/when-not-to-use guidance relative to siblings, no mention of partial-update expectations, and no prerequisites such as permissions or design existence.

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