Skip to main content
Glama
Sign In
LTspice MCP

LTspice MCP

by kh6570
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Add Hierarchical Block

add_hierarchical_block

Create a child sheet with In/Out pins and place it on the parent schematic, enabling hierarchical blocks in LTspice.

Instructions

Create a child sheet with In/Out pins and place it on the parent.

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>",
      "block_name": "<block_name>",
      "reference": "<reference>"
    },
    "name": "add_hierarchical_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
referenceYes
block_nameYes
schematic_pathYes
workspace_rootNoOptional per-call workspace root override.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly, non-destructive, non-idempotent write, so the safety profile is covered. The description usefully adds that a child sheet, In/Out pins, and a parent placement are produced, but it omits failure behavior, whether the parent is mutated in place, or what happens on repeat calls.

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?

A single front-loaded sentence with no filler and the action stated first. It is efficient, though its brevity borders on under-specification for a 6-parameter editing 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 hierarchical-schematic mutation with 6 parameters, no output schema, and near-zero schema coverage, one sentence is inadequate. An agent is left guessing what reference, x, and y do and what preconditions must hold before the call.

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 coverage is only 17% (only workspace_root is documented), so the description must compensate and does not. Terms like 'child sheet', 'In/Out pins', and 'parent' loosely gesture at block_name/schematic_path, but x, y, and reference are never explained in either the schema or the description.

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 ('Create a child sheet'), plus the side effects of adding In/Out pins and placing it on the parent. It is clear what the tool does, but it never distinguishes itself from nearby siblings like add_component or create_schematic, so an agent can't route on the description alone.

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 guidance, no prerequisites (e.g. whether a parent schematic must already exist or be loaded), and no mention of alternatives like add_component. The agent must infer usage entirely from the name and title.

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