Skip to main content
Glama
Sign In
LTspice MCP

LTspice MCP

by kh6570
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Components

list_components
Read-onlyIdempotent

Retrieve all placed components from an LTspice .asc schematic by path to inspect or verify circuit contents.

Instructions

List placed components.

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

Input Schema

NameRequiredDescriptionDefault
schematic_pathYes
workspace_rootNoOptional per-call workspace root override.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and closed-world, so the safety profile is fully covered by structured data. The description adds nothing on top — no indication of scope (whole schematic vs. a sheet), ordering, pagination, or result size, which is the kind of context that would actually earn credit here.

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 zero filler, which is structurally clean. The problem is under-specification rather than verbosity, so it lands at the minimum-viable level.

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, the description carries the burden of explaining what is returned (component identifiers, references, values?) and in what shape. It says only 'placed components', leaving the return contract and the required schematic_path semantics unexplained.

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 50%: workspace_root is documented but schematic_path is not. The description contributes no parameter meaning at all, so it fails to compensate for the undocumented required path parameter.

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 ('List placed components'), so the agent knows exactly what operation is performed. However, it does nothing to distinguish itself from close siblings like read_component, inspect_schematic, or list_subcircuits, which an agent could easily confuse with it.

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 guidance on when to use this versus alternatives such as read_component (single component detail) or inspect_schematic (broader survey). No prerequisites, no scoping conditions, nothing to route the agent among the many sibling list/read tools.

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