vcf-ops-mpb-mcp

Get one design item

mpb_get_item

Read-only

Retrieves the full form for a request, object, relationship, or event, including referenced data. Use itemId "default" for a blank, defaults-filled new-item template.

Instructions

Returns the full form for one request, object, relationship or event (the item plus what it can reference). Use itemId "default" for a blank, defaults-filled form to base a new item on.

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>",
      "section": "<section>",
      "itemId": "<itemId>"
    },
    "name": "mpb_get_item"
  }
}

Input Schema

Name	Required	Description
`itemId`	Yes	Item UUID, or "default" for a new-item template
`section`	Yes	Design section: requests, objects, relationships or events
`designId`	Yes	MPB design UUID (see mpb_list_designs)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 15, 2026

TDQS

A4.2/5.0

Behavior4/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 the safety profile is covered. The description adds value beyond that by disclosing the payload shape (the item plus its referenceable data) and the special 'default' semantics that produce a synthetic, non-persisted form rather than an existing record — important given there is no output schema.

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 sentences, both front-loaded with the resource then the special-case parameter. Nothing is repeated and no sentence is 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 3-parameter read tool with full schema coverage, annotations covering safety, and no output schema, this is sufficient: it explains what comes back and the one parameter value that behaves unusually. Error behavior for an unknown itemId is the only minor omission.

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 100%, so the baseline is 3, but the description earns a bump by explaining what the "default" itemId actually yields ('a blank, defaults-filled form to base a new item on'), which is more informative than the schema's terse 'new-item template'. The designId and section parameters are left entirely to 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 names a specific verb and resource: it returns 'the full form for one request, object, relationship or event,' including what the item can reference. That is far more precise than the title alone, though it never distinguishes itself from siblings such as mpb_get_design (whole design) or mpb_upsert_item (write path).

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?

It gives clear usage context: call this to read a single item's full form, and pass itemId "default" when you want a defaults-filled blank to base a new item on — a non-obvious routing hint toward item creation. It stops short of explicit exclusions (e.g., 'use mpb_get_design to fetch the whole design'), so it is context without alternatives.

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