Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Add P&ID items

add_pid_items

Add P&ID symbols to a project with auto-assigned tags and layout; link items to wiring components so the project tag rule prints the correct tag.

Instructions

Add symbols to the project's P&ID (list_pid_symbols has the keys). With no tag an item gets the next free one (I-1, V-1, P-1, TK-1, E-1; actuators get none). With no position the auto-layout places it. size is for equipment only and snaps to the symbol's 10-unit steps. With component, the item links to that wiring component and the project's tag rule decides what it prints, so the result shows the printed tag.

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": {
      "project_id": "<project_id>",
      "items": "<items>"
    },
    "name": "add_pid_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare it is a non-read-only, non-destructive, closed-world write, so the description's job is to add context — and it does: the concrete auto-tag sequence (I-1, V-1, P-1, TK-1, E-1; actuators excluded), auto-layout on missing position, and 10-unit size snapping. It stops short of saying whether the batch is atomic, what is returned (item ids for later update/remove), or how conflicts on user-supplied tags are handled.

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?

Four dense sentences, each front-loaded with its condition ('With no tag…', 'With no position…', 'With component…'), and no filler. Parenthetical pointers to the sibling lookup tool are useful, not decorative.

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 batch-create tool with no output schema and an undocumented top-level items array, the description covers the risky defaults well enough to call it correctly. The main remaining gap is return value / handle for the created items, which matters because sibling update and remove tools exist.

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?

Top-level schema coverage is reported at 0%, so the description must carry the weight, and it explains the meaning of tag, at, size, and component beyond their field descriptions. It leaves props and location (the ISA bubble enum) unaddressed, so it does not fully compensate.

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?

States a specific verb and resource ('Add symbols to the project's P&ID') and immediately redirects to list_pid_symbols for valid keys, which separates it from sheet/line/item-mutation siblings such as add_pid_sheet or update_pid_items.

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?

Gives clear conditions for the tool's default behaviors (omit tag -> next free prefix tag; omit position -> auto-layout; supply component -> link to wiring component). It does not explicitly say when to prefer update_pid_items or remove_pid_items over this tool, so no exclusion guidance is present.

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