Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Link instrument

link_instrument

Link or clear a P&ID item's wiring component by tag; the result shows the tag chosen by the project's tag rule.

Instructions

Link a P&ID item to a wiring component by tag, or clear the link with component null. The project's tag rule decides which tag the item prints, and the result shows it.

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>",
      "item": "<item>",
      "component": "<component>"
    },
    "name": "link_instrument"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesP&ID item tag or id
componentYesWiring component tag, or null to clear the link
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the write-but-safe profile is known. The description adds genuine context beyond that: the project's tag rule determines which tag the item prints, and the result reflects it. It omits whether re-linking overwrites an existing link and how an unresolvable tag is reported, which matters for a mutation 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?

Two tight sentences: the operation and its clear-mode come first, followed by one sentence of useful downstream context. Nothing is repeated or wasted.

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?

There is no output schema, so the description should carry return-value information, but it only says vaguely that 'the result shows it' rather than stating what is returned. The core operation is adequately covered for a three-parameter mutation tool, but the response shape and error conditions remain unstated.

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 coverage is 67%, with 'item' and 'component' both described in the schema, including the null-clears semantics. The description reinforces that linking is by tag rather than id and explains the tag-rule resolution, but 'project_id' is undocumented in both places. Baseline 3 is appropriate given the schema does most of the work.

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 gives a specific verb ('Link') plus both resources ('P&ID item', 'wiring component') and covers the inverse operation ('clear the link with component null'). It does not differentiate against siblings, though no sibling in the provided list appears to perform the same linking action, so the gap is minor.

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 states the two modes of use clearly: pass a component tag to create the link, pass null to remove it. It does not cover prerequisites (e.g. whether the component must already exist) or what happens if the tag is unknown or an item is already linked, so there is no explicit when-not guidance.

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