Skip to main content
Glama
Sign In
LTspice MCP

LTspice MCP

by kh6570
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Read Subcircuit

read_subcircuit
Read-onlyIdempotent

Retrieve a .subckt body or hierarchical sheet from an LTspice schematic so you can inspect or reuse its contents.

Instructions

Return one .subckt body or a hierarchical sheet.

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": {
      "source_path": "<source_path>",
      "name": "<name>"
    },
    "name": "read_subcircuit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
source_pathYes
workspace_rootNoOptional per-call workspace root override.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds essentially nothing beyond that — no return format, no error behavior, no note on what a hierarchical sheet read entails.

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. It is efficiently sized for what it says, though brevity here reflects under-specification rather than discipline.

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?

With no output schema, two of three parameters undocumented, and no usage guidance, the definition leaves significant gaps for a read tool. Annotations cover safety, but an agent still lacks enough to invoke it confidently.

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 33%: source_path and name (both required) carry no schema descriptions, and the description does not compensate with any meaning for them. Only workspace_root is documented. The low coverage means the description should add parameter context but does not.

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 (Return) and resource (.subckt body / hierarchical sheet), which distinguishes it from siblings like list_subcircuits and read_component. However, the 'or a hierarchical sheet' clause is vague and it doesn't clarify the relationship to list_subcircuits.

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?

No when-to-use guidance is provided. It never explains when to reach for read_subcircuit versus list_subcircuits, inspect_schematic, or read_component, nor what preconditions (e.g. valid source_path) are needed.

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