Skip to main content
Glama
Sign In
ltspice-mcp

ltspice-mcp

by xuio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

listLtspiceLibraryEntries

List LTspice symbol entries from ZIP archives, with optional query filtering to quickly locate specific .asy files.

Instructions

List LTspice symbol ZIP entries (.asy), optionally filtered by query.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listLtspiceLibraryEntries"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
limitNo
lib_zip_pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.32.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations exist, so description must disclose behavior. It mentions optional query filtering but omits details like read-only nature, default limit of 200, or any side effects. Lacks transparency for a listing operation.

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?

Single sentence is concise and front-loaded, but omits critical parameter information. Passable for a simple tool but under-specified for three optional parameters.

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?

Despite having an output schema, the description fails to explain parameter roles (query, limit, lib_zip_path), especially important since schema has no descriptions. Agent would need to guess or rely on sibling tool patterns.

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 0%, but description only hints at query filtering without explaining format or purpose. No mention of limit or lib_zip_path parameters, leaving agents to infer from defaults.

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?

Clearly states it lists LTspice symbol ZIP entries with file extension .asy, distinguishing it from sibling tools like listLtspiceSymbols which likely lists symbol names rather than ZIP entries.

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 guidance on when to use this tool versus alternatives such as listLtspiceSymbols or getLtspiceSymbolInfo. No context or exclusions provided.

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