Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Add components

add_components

Place existing Codex parts into a project under unique tags and optional subsystems to build or update wiring designs. Add one or more components in a single call.

Instructions

Place Codex parts in a project under unique tags (e.g. PLC_MAIN, PSU1, K1). The part must already exist in the Codex (search_codex / save_part). subsystem = name or id of an existing subsystem.

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>",
      "components": "<components>"
    },
    "name": "add_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
componentsYes
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, non-read-only, closed-world mutation, so the safety profile is covered. The description adds two useful constraints beyond that: tags must be unique and the subsystem must already exist. It is silent on what happens when a tag collides (error vs overwrite) and on whether the whole batch is atomic when one component fails.

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 sentences, no filler, with the core action first and the prerequisite second. Every clause adds information an agent needs.

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?

With no output schema and a nested components array, the description leaves the response shape and per-item failure behavior unspecified, and duplicate-tag handling is unstated. It covers the essentials for invoking the tool but not the outcome semantics an agent needs to verify success.

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 description coverage is 0%, so the description must carry the load, and it does reasonably well: it explains tag uniqueness with concrete examples (PLC_MAIN, PSU1, K1), clarifies that subsystem accepts a name or an id of an existing subsystem, and implies part_id must reference an existing Codex part. project_id is left unexplained, and the nested array shape is only implied.

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?

States a concrete verb and resource: placing existing Codex parts into a project under unique tags. The reference to search_codex / save_part as the way parts come to exist separates it from part-creation tools, though it doesn't distinguish itself from sibling wiring tools like add_connections or add_cable.

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?

Gives a clear prerequisite ('The part must already exist in the Codex') and names the tools to use first (search_codex / save_part), which is real routing guidance. It does not say when to prefer update_components or remove_components instead, so the when-not-to-use side is absent.

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