Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Add P&ID sheet

add_pid_sheet

Adds a named print sheet to a P&ID with a 1504×800 frame at given x,y coordinates and reports the items assigned to each sheet.

Instructions

Add a named print sheet to the P&ID: a frame of 1504 × 800 units with its top-left at x,y. An item prints on the sheet holding its centre, sheets print in the order listed, and items outside every sheet tile onto automatic sheets after them. 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>",
      "name": "<name>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "add_pid_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
nameYes
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, closed-world mutation, and the description adds real behaviour on top: fixed frame dimensions, centre-based item assignment, ordered printing, and implicit auto-generated sheets for items outside every tile. It does not say what happens on a duplicate name or whether the call is idempotent, which keeps it below a 5.

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 clauses, front-loaded with the creation action and its geometry before the printing rules. Every sentence carries information about creation, placement, or the returned result; nothing is padded.

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, the description correctly notes that the result lists what each sheet holds, and it explains the side effect of auto-generated sheets. It falls short only on project_id scoping and error/duplicate-name behaviour for a four-required-parameter mutation.

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 0%, so the description must carry parameter meaning, and it does explain name (a named sheet) and x/y (the top-left corner of the frame). The required project_id is never mentioned, so one of four parameters remains undocumented in both schema and description.

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?

The description gives a specific verb and resource ('Add a named print sheet to the P&ID') and then defines the resource geometrically as a 1504 x 800 frame with its top-left at x,y. That definition makes it unmistakable against the update/remove sheet siblings, which act on an existing sheet rather than creating one.

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 described printing semantics: an item prints on the sheet holding its centre, and leftover items tile onto automatic sheets. However, it never states when an agent should call this rather than update_pid_sheet, or whether sheets must exist before add_pid_items is used.

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