Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Create or update a signal type

save_signal_type

Create or update a wire signal type to define what a wire carries and the color it draws; set gauge, voltage, category, and visibility.

Instructions

Create a signal type (what a wire carries and the color it draws in), or update one you own (pass signal_id). Comms types draw dashed and let a terminal take several wires without a fan-out. Free users' signal types are always public; Pro ones default to private. Built-in types are read-only.

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": {
      "name": "<name>",
      "color": "<color>"
    },
    "name": "save_signal_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
awgNoDefault wire gauge, AWG: "18", "14", "1/0". null clears it.
mm2NoDefault wire gauge as a cross-section in mm², e.g. 0.75. null clears it. Set either or both.
nameYes
colorYesInsulation color as hex, e.g. #7C3AED
voltsNoNominal voltage of this signal, e.g. 24 or 120; the voltage-drop check divides by it. null clears it (no drop check).
dashedNoDraw dashed (cables / comms). Default: true for comms
phasesNo1 for DC and single-phase (the default), 3 for three-phase (√3 in the drop formula). null clears it (treated as 1).
publicNo
categoryNoother
signal_idNo
color_nameNoReadable color name, e.g. "Violet" or "White/Blue"
stripe_colorNoTracer stripe as hex, or null for none

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare that this is a non-destructive, closed-world write. The description adds real domain behavior beyond that: built-in types cannot be modified, visibility defaults differ by plan tier, and comms types draw dashed and permit several wires on a terminal without a fan-out. It does not say whether an update replaces or merges omitted fields, which matters for a save/upsert tool with null-clears semantics.

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?

Four short sentences, front-loaded with the create/update distinction before the domain rules. Every sentence carries information, though the comms/dashed sentence is somewhat dense and reads as domain trivia until the agent reads the schema's dashed parameter.

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?

For a 12-parameter mutation tool with no output schema and sparse annotations, the description covers identity, mode, permissions-by-tier and built-ins, which is the important part. It leaves unstated whether an update is a full overwrite or a partial merge, and says nothing about the returned value or what happens on a name collision.

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?

At 67% schema description coverage the schema already documents awg, mm2, volts, phases, color, dashed, color_name and stripe_color in detail. The description adds meaning only for signal_id (update mode) and partially for color/dashed (comms draw dashed and allow multiple wires per terminal without a fan-out). It says nothing about category, public, or the interaction between awg and mm2, so it adds marginal value over the schema.

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?

"Create a signal type ... or update one you own (pass signal_id)" names a specific verb and resource and clarifies the tool's dual create/update mode, which resolves the main ambiguity an agent would have. It does not name a sibling (e.g. list_signal_types) to contrast with, so it stops short of explicit sibling differentiation.

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?

The description clearly states the mode switch: call without signal_id to create, pass signal_id to update something you own. It also gives a hard exclusion (built-in types are read-only) and a visibility rule (free users' types are always public, Pro defaults to private). No alternative tools are named for looking up existing types before saving, which keeps it below a 5.

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