Skip to main content
Glama
Sign In
LTspice MCP

LTspice MCP

by kh6570
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Add Component

add_component

Place a primitive component in an LTspice schematic by specifying its kind, reference, and position. Use it to add resistors, capacitors, and other primitives to .asc files.

Instructions

Place a primitive component.

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": {
      "schematic_path": "<schematic_path>",
      "kind": "<kind>",
      "reference": "<reference>"
    },
    "name": "add_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
kindYes
valueNo
rotationNo
referenceYes
schematic_pathYes
workspace_rootNoOptional per-call workspace root override.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: no word on the coordinate system, whether placement auto-routes or renumbers references, or what happens on a duplicate reference.

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?

A single front-loaded sentence with no filler, but the brevity here is under-specification rather than disciplined concision for an 8-parameter mutation tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a write operation with 8 parameters, 3 required, no output schema, and near-zero schema coverage, the definition is far too thin. An agent cannot confidently construct a call from this description plus the bare schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 13% (just workspace_root), so the description must compensate and does not. It says nothing about x/y units or coordinate origin, allowed 'kind' values, rotation format, value semantics, or the schematic_path requirement, leaving 7 of 8 parameters undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('place' + 'primitive component'), and 'primitive' hints it is for built-in parts rather than library parts. However, it never distinguishes itself from close siblings such as add_library_component, add_component_from_asy, or add_component_symbol_drawing, so the agent must guess which adder applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use, when-not-to-use, or alternative-routing guidance at all. Given that ~10 sibling tools also add schematic elements, this absence is a real selection hazard.

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

Deploy Server

Other Tools