Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Update P&ID sheet

update_pid_sheet

Rename a placed P&ID sheet, move its frame using top-left x/y coordinates, or change its print order. Returns a list of what each sheet holds.

Instructions

Rename a placed P&ID sheet, move its frame (x,y is the top-left), or change where it prints (position, 1 = first). sheet is its id or name. The result lists what each sheet holds.

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>",
      "sheet": "<sheet>"
    },
    "name": "update_pid_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
nameNo
sheetYes
positionNoPlace in print order among the placed sheets
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world mutation, and the description adds useful detail: x/y is the top-left corner, position is print order with 1 = first, and the return value summarizes sheet contents. It does not say what happens to unspecified fields or whether moving a frame affects contained items.

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?

The three capabilities are front-loaded, and the follow-up sentences handle the sheet identifier and return value without padding. Minor density issues ('position, 1 = first') but no wasted sentences.

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 six-parameter mutation tool with no output schema, the description covers the optional field semantics and sketches the return value, which is good. Gaps remain around project_id's role and around whether the operations are independent or combinable in one call.

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?

With only 17% schema coverage, the description carries the load and largely does: it maps name to renaming, x/y to the frame's top-left, position to print order with a 1-based convention, and clarifies that sheet accepts an id or a name. Only project_id is left undefined.

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 resource (a placed P&ID sheet) and three concrete operations: rename, move frame, change print position. It is clearly distinct from siblings like add_pid_sheet, remove_pid_sheet, and update_pid_items, though it never explicitly contrasts itself with them.

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 enumeration of the three editable aspects (name, frame x/y, print position), so an agent can infer when to pick this tool. There is no explicit when-not guidance, no mention of prerequisites, and no statement that at least one change must be supplied.

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