Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Add process lines

add_process_lines

Draw process, signal, or other lines between P&ID items by connecting tag ports, so piping and instrumentation connections appear on the diagram.

Instructions

Draw lines between P&ID items. from and to are "TAG:PORT" or "TAG" (tag or item id; list_pid_symbols has each symbol's ports, and a bare side like 90 on a side with several ports takes the one closest to the other end, so the line runs straight when a port lines up; with no positions, the one closest to the side's centre). kind defaults to process. Signal lines come from the wiring, so draw one only for something not wired yet. A line from an item to itself or an exact duplicate is skipped.

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>",
      "lines": "<lines>"
    },
    "name": "add_process_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesYes
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 this is a non-read-only, non-destructive, closed-world mutation. The description adds real behavioral context beyond that: self-lines and exact duplicates are silently skipped, and bare-side ports are resolved by proximity heuristics. It does not say what the response contains, but the skip behavior is the important disclosure.

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?

It is front-loaded with the core action and every sentence carries information. The nested parentheticals about port selection are dense and slightly hard to parse on first read, but nothing is wasted.

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 mutation tool with no output schema and annotations covering the safety profile, the description supplies the port-resolution rules, the default kind, and the duplicate-skip behavior. Only the return value and project_id scoping are unaddressed, which are minor.

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 0%, so the description must carry the load, and it largely does: it defines the 'TAG:PORT' / 'TAG' format for from and to, explains port-selection fallbacks, and states that kind defaults to process. The label field is left to its schema description, and project_id is unmentioned, but the hard part of the parameter semantics is covered.

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 opens with a specific verb and resource: 'Draw lines between P&ID items.' That is unambiguous and distinct from add_connections or add_cable, though it never explicitly contrasts itself with those siblings. The agent can tell what the tool does without opening the schema.

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 a concrete when-not rule: 'Signal lines come from the wiring, so draw one only for something not wired yet,' and points to list_pid_symbols for port discovery. It does not name a sibling for the general connection case, but the guidance is clear enough to act on.

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