Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Update project settings

update_project

Change a project's name, status, visibility, signal flow, title-block fields, sizing standard and ampacity column, length unit, voltage-drop limits, or spare-terminal percentage.

Instructions

Rename, change status/visibility (Pro/Student only for private), default signal flow, title block fields, the sizing standard and its ampacity column, the length unit, the voltage-drop limits, or the spare-terminal percentage. title_block keys are the PDF template's field ids (built-in: drawingNo, drawnBy, customer, rev; custom template fields have their own ids).

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": "update_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowNo
titleNo
statusNo
ambient_cNoAmbient temperature the ampacity is corrected for, in °C (0–100). null = the default 40 °C (inside the enclosure).
pid_sheetsNoPDF: P&ID sheets after the schematic (default on when the project has P&ID items).
project_idYes
visibilityNo
gauge_unitsNoWire gauge units in the grid, labels and PDF (default awg). In mm2 projects a bare gauge number means mm².
harness_minNoFewest wires between two subsystems that make a harness (one trunk line). Default 3; null resets it.
length_unitNoUnit lengths are entered and shown in (default ft). Stored lengths are metres either way.
pack_on_fixNofix_fanouts / Fix all re-pack the strips they touch.
title_blockNo
strip_namingNoTags for new strips: tb = TB1 / TB-PWR1 (default), iec = -X1, -X2. Existing strips keep their tags.
strip_reportNoPDF: a terminal strip report page per strip (default true).
default_blockNoTerminal block part (id or part number) new strips and strip terminals use when none is picked. null = generic block.
sizing_columnNoAmpacity / insulation column of the standard (e.g. "75C", "105C-outside"); must be one of its columns. null = the standard's default.
sizing_reportNoPDF: a sizing report page, one section per fuse or breaker (default on when any wire has sizing data).
drop_total_pctNoTotal voltage-drop limit to the supply, in % of the signal's volts (0–100). null = the default 5 %.
harness_reportNoPDF: a breakout table per harness (default true).
drop_branch_pctNoBranch voltage-drop limit — from the last fuse or breaker to the load — in % of the signal's volts (0–100). null = the default 3 %.
gauge_on_labelsNoPrinted wire labels include the gauge ("24VDC (+) 18 AWG BU"). Default false.
sizing_standardNoSizing standard behind gauge and fuse suggestions (default nec). electronics: dev boards, breakouts and header pins, ampacity down to 30 AWG and no minimum size on DC or signal wires.
default_pe_blockNoSame, for protective-earth strips. null = generic PE block.
spare_terminal_pctNoPacking (Clean up, fix_fanouts) appends this many spare terminals per strip, in % of its used terminals (0–50), empty and unlocked at the end. null = none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/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 safety is partly covered. The description adds useful behavioral detail — that title_block keys are PDF template field ids with named built-ins, that existing strips keep their tags under strip_naming, and that spare terminals are appended empty and unlocked — but says nothing about permissions, whether partial updates merge or replace, or what is returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences front-load the list of mutable settings, which is efficient for a 24-parameter tool, and the second sentence earns its place by explaining title_block keys. The long comma-separated enumeration is dense and reads as a parameter dump rather than structured guidance, and there is no grouping by concern.

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 large-optional-field update tool with no output schema, the description covers what can be changed plus the one non-obvious parameter format. The remaining gap is the absence of any statement about atomicity/partial-update behavior and the default-ft/metre storage nuance, which the schema already carries per-field.

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 75% and the description adds real meaning for the least self-documenting parameter: title_block is explained as a map from the PDF template's field ids, with the built-in ids listed. However, many other parameters (status, visibility, flow, title) are not elaborated in the description, and the merge-versus-replace semantics of a 24-parameter partial update are never stated.

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 enumerates the settings it mutates (title, status/visibility, signal flow, title block fields, sizing standard/column, length unit, voltage-drop limits, spare-terminal percentage). It clearly distinguishes itself from siblings like create_project or update_page by naming the project-level settings it touches, though it does not explicitly name a sibling alternative.

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?

The only usage constraint given is "Pro/Student only for private" visibility, which is a genuine precondition. There is no explicit statement of when to use update_project versus update_page/update_components/update_subsystem, so routing is mostly implied by the resource name.

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