vcf-ops-mpb-mcp

Get MPB design detail

mpb_get_design

Read-only

Retrieve an MPB design's details, validation status with per-section errors, and optional source, configuration, request, object, relationship, and event lists by design UUID.

Instructions

Returns a design: info, validation status (with per-section errors) and, if requested, the source, source configuration and the request/object/relationship/event lists.

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

Input Schema

Name	Required	Description	Default
`include`	No	Extra parts to fetch. Default: sourceSummary plus all four section lists.
`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.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuine context about the response shape, notably that validation status carries per-section errors and that source/configuration/lists are conditional. It does not mention payload size, cost of fetching all lists, or permission requirements.

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?

A single front-loaded sentence that puts the guaranteed content first and the optional content last, mirroring the include semantics. The long enumeration is dense but every item earns its place by telling the agent what can be retrieved.

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?

With no output schema present, the description carries the burden of describing returns and does so adequately by naming each section and noting per-section validation errors. A tool with a 2-parameter, fully documented schema and read-only annotations needs little more; only guidance on when defaults apply or how large responses behave is missing.

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 description coverage is 100%: the include enum and its default (sourceSummary plus all four section lists) are documented in the schema, as is designId. The description merely restates that extra parts are available when requested, adding no syntax, ordering, or interaction detail beyond the schema.

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?

The description opens with a specific verb and resource ("Returns a design") and enumerates the payload: info, validation status with per-section errors, and the optional source/configuration/section lists. It is clear what the tool produces, but it never distinguishes itself from the sibling mpb_get_design_status, which an agent could plausibly confuse it with.

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?

Usage is only implied: the phrase "if requested" signals that extra parts are opt-in, and the sibling reference in the designId schema hint (see mpb_list_designs) helps with discovery. There is no explicit statement of when to choose this over mpb_get_design_status or mpb_export_design, and no exclusions.

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