Skip to main content
Glama
SpiceMCP
by oniondas

find_part

Locate a real SPICE part by part number or manufacturer in local LTspice and configured libraries, then use the returned name in template-based circuits.

Instructions

Find a real part by part number or maker in the SPICE libraries on this computer (LTspice's, plus SPICEMCP_LIB_DIRS). Use the name in start_from_template parts.

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": {
      "query": "<query>"
    },
    "name": "find_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoany
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the search targets on-machine libraries (LTspice's plus SPICEMCP_LIB_DIRS), which explains why results vary by install, but leaves match semantics (partial/exact, case sensitivity), multi-hit versus single-hit behavior, and empty-result behavior unstated.

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?

Two short sentences with the core purpose front-loaded and the library-scope qualifier immediately after. No redundant restatement of the tool name and no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only lookup with no output schema and no annotations, the definition covers what the tool searches and why. Gaps remain around result shape (single best match versus ranked list) and the meaning of 'kind', which an agent needs in order to interpret an ambiguous or empty reply.

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%, so the description must compensate for both parameters. It clarifies that the query may be either a part number or a maker name, which is genuinely additive, but says nothing about the 'kind' enum or whether it narrows the search to a device class, leaving half the parameters undocumented everywhere.

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 ('Find a real part by part number or maker') and scopes the search to local SPICE libraries including LTspice's and SPICEMCP_LIB_DIRS. It does not fully separate itself from the sibling list_templates or explain how its results relate to check_feasibility, but the lookup-versus-design distinction is legible.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the phrase 'Use the name in start_from_template parts,' which describes a downstream consumer rather than when to choose this over list_templates or another sibling. There is no when-not guidance or statement about what to do when no match is found.

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