ltspice-mcp

by xuio

Overview Schema Source Related Servers Discussions Admin

Python

Local

listJobs

List queued, running, or completed simulation jobs with filtering by status, limit, and order.

Instructions

List queued/running/completed simulation jobs.

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": "listJobs"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`status`	No
`order_by`	No	created_at
`include_history`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.32.0Jun 10, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits beyond the obvious read-only operation. It lacks information about rate limits, authentication requirements, or how failures are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly conveys the purpose without any superfluous words or structural issues.

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?

Given the tool's complexity (4 optional parameters, presence of an output schema, and many sibling tools), the description is too brief. It omits details about pagination, filtering behavior, and return format, making it incomplete for effective decision-making.

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

Parameters1/5

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

With 0% schema description coverage and 4 parameters, the description adds no meaning beyond the schema. It does not explain what 'limit', 'status', 'order_by', or 'include_history' do, leaving the agent uninformed.

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

Purpose5/5

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

The description explicitly states the action (List) and the resource (simulation jobs) and further specifies the scope (queued/running/completed), making it clear and distinguishable from sibling tools like cancelJob or queueSimulationJob.

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 tool versus alternatives (e.g., jobStatus for a single job, listJobHistory for past jobs). No context about prerequisites or scenarios where this tool is particularly appropriate or inappropriate.

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

Deploy Server