Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Add terminals to a Codex part

add_part_terminals

Adds terminals to a Codex part with optional load and rated current data, preserving existing part data and forking non-editable parts into your Codex.

Instructions

Add terminals to a Codex part. Terminals can carry load_a / rated_a current data (datasheet values, not guesses); the part's other data stays as it is. Your own parts, and team parts in a team where you're an editor or up, are changed in place; anything else is forked into your Codex first (into the team's Codex when project_id is a team project). Pass project_id to relink that project's components to the fork.

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": {
      "part_id": "<part_id>",
      "terminals": "<terminals>"
    },
    "name": "add_part_terminals"
  }
}

Input Schema

NameRequiredDescriptionDefault
part_idYes
terminalsYes
project_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, destructive=false, openWorld=false) by disclosing merge semantics ('the part's other data stays as it is'), the fork-on-no-permission behavior, the destination Codex for team projects, and the relink side effect of project_id. It also warns that current values must be datasheet values, not guesses.

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?

Three tight sentences, front-loaded with the purpose before the permission/fork rules. The parenthetical 'datasheet values, not guesses' is the only slightly editorial phrase, but it conveys a real data-quality constraint rather than filler.

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 mutation tool with no output schema, it covers the important unknowns: what is preserved, what gets forked, who may edit in place, and the project_id side effect. It leaves out what the call returns (e.g., fork identifier) and how duplicate or existing terminals are handled, which would matter for an agent chaining calls.

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?

Top-level parameters (part_id, terminals, project_id) carry no schema descriptions, so the description must compensate; it explains project_id's relink effect and mentions load_a/rated_a, but says nothing about part_id's meaning or the per-terminal object shape. The nested terminal fields are documents in the schema, which offsets the gap but leaves the top level partially covered.

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 specific verb and resource ('Add terminals to a Codex part') and narrows scope to the part's terminal data only. It does not explicitly contrast with nearby siblings such as add_components or add_terminal_strip, so the agent must infer the boundary, but the operation itself is unambiguous.

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 concrete selection context: in-place edits for your own parts and team parts where you are editor or above, forking otherwise, plus when to pass project_id. It stops short of stating when to prefer this over related add_* tools, but the permission and fork conditions are clearly laid out.

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