Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Add wires

add_connections

Append wires between component terminals to extend a wiring schematic and return validation issues after the change.

Instructions

Append wires (grid rows) between component terminals. Terminals must exist on the Codex part; terminal strips accept new terminal labels. Returns the issues after the change.

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>",
      "wires": "<wires>"
    },
    "name": "add_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
wiresYes
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations declare a non-read-only, non-destructive mutation, and the description adds the important fact that the call reports issues after the change, which matters because there is no output schema. It does not say whether a bad terminal aborts the whole batch or whether issues mean partial application. With annotations already covering the safety profile, a 3 is appropriate.

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 short sentences, no filler, purpose and precondition front-loaded ahead of the return note. Every sentence carries information an agent needs.

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 two-parameter mutation with no output schema, the definition covers purpose, prerequisites, and post-call behavior. It leaves open duplicate handling and the relationship with allow_multiple_wires, which are the remaining gaps.

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?

Reported schema coverage is 0% at top level, so the description must compensate. It does clarify the domain meaning of from/to ('TAG:TERMINAL', terminals must exist, strips accept new labels), which genuinely helps. It says nothing about draw, gauge, bundle, length, or signal, which the nested schema does document, so the burden is only partly carried.

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 concrete verb plus resource: 'Append wires (grid rows) between component terminals.' That is specific enough to tell it apart from add_cable or import_wiring_list by inference, since wires are called out as grid rows between terminals. It does not explicitly name a sibling, so it stops short of a 5.

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?

A real prerequisite is given: terminals must already exist on the Codex part, and terminal strips accept new terminal labels. What is missing is guidance on when to choose this over add_cable for cable conductors, or over import_wiring_list for bulk wiring. Usage is implied rather than fully routed.

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