Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Update P&ID items

update_pid_items

Modify placed P&ID item properties—position, size, symbol, tag, location, and props—without moving connected lines; tag changes follow project rules.

Instructions

Change placed P&ID items without touching their lines: position, size, symbol, tag, location, props. Lines keep their spot through a resize or symbol change. A tag follows the project's tag rule: renaming an item linked under the "same" rule renames its wiring component too. A blank location unsets it, and so does a blank props field.

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": "update_pid_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare non-read-only, non-destructive, closed-world; the description adds genuinely non-obvious behavior: line endpoints survive resize/symbol changes, tag renames cascade to the wiring component under the 'same' rule, and blank location/props values unset rather than ignore. It stops short of saying whether omitted fields are left untouched, which matters for a partial-update tool.

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?

Three tight sentences, front-loaded with the verb and scope, then the line-preservation guarantee, then the tag-rule and unset edge cases. No filler or restatement of the title.

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 nested-array mutation tool with no output schema, the description covers the fields, side effects, and unset semantics well. It omits return/response behavior and whether the update is partial or full-replacement, which an agent would want before calling.

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 description coverage is 0%, so the description must carry the load, and it does map the six item fields (position, size, symbol, tag, location, props) and explains the empty-string unset semantics for location and props. It does not clarify the item identifier field or the at/x-y coordinate shape, leaving some schema-level ambiguity.

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 (change) and resource (placed P&ID items) and enumerates the mutable fields: position, size, symbol, tag, location, props. The scoping phrase 'without touching their lines' cleanly separates it from line-editing siblings and from add_pid_items/remove_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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the field list and the note that lines keep their spot through resize or symbol change, which tells an agent this is the right tool for in-place edits. However, it never explicitly says when to prefer this over add_pid_items or remove_pid_items, nor states prerequisites such as the project needing to exist or items being already placed.

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