Skip to main content
Glama
Sign In
IntelligentElectron

Universal Netlist MCP Server

by IntelligentElectron
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List components

list_components
Read-onlyIdempotent

Lists components of a specified refdes prefix in a design, matches whole prefixes case-insensitively, groups identical parts, and optionally includes DNS parts.

Instructions

List components of a specific type in a design. The type is the refdes prefix, matched whole and case-insensitively: "u" gives U1 and U2 but NOT USB1, whose prefix is USB, and "tp" gives the test points. Asking for a partial prefix returns nothing rather than everything starting with it, so if a part you expected is missing, look for it under its own prefix. Identical components are grouped for compact output: parts share a group only when their MPN, description, comment and value all agree, so every field a group reports is true of every part in it. component_notes names the parts with no MPN. If no components match, the error lists the prefixes the same query would return, and names apart any prefix whose components are all DNS. A prefix whose components are all DNS returns an empty list with a note saying so; pass include_dns=true to list them.

Input Schema

NameRequiredDescriptionDefault
typeYesComponent prefix: U, C, R, L, etc.
designYesPath to design file, as returned by list_designs
include_dnsNoInclude DNS (Do Not Stuff) components, flagged dns=true. Pass false to list only fitted parts
design_variantNoDesign variant name from list_designs' design_variants. Required when the design records named variants, which are its only builds. <Default> (alias: default) is the one build of a design that records none

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0-development

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, closed-world), and the description adds substantial context beyond them: grouping rules, component_notes behavior, the pattern of error responses listing candidate prefixes and all-DNS prefixes. One flaw: it says to "pass include_dns=true to list them," while the schema declares include_dns defaults to true, leaving the actual default behavior ambiguous.

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?

Dense but front-loaded: the matching rule comes first, then grouping, then edge-case/error behavior. A couple of clauses restate the same idea ("every field a group reports is true of every part in it"), so it is slightly longer than strictly needed.

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

Completeness4/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 must carry return-shape burden, and it does explain grouping and the note-bearing empty result. The remaining gap is the include_dns default discrepancy, which could lead an agent to expect an empty list where DNS parts are actually returned.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents all four parameters (baseline 3). The description still adds real semantic value for `type`: whole-word and case-insensitive matching, and that partial prefixes return nothing rather than a superset.

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?

States a specific verb and resource ("List components") plus the scoping dimension (component type/refdes prefix in a design). The whole-word, case-insensitive prefix rule effectively separates it from the search_components_by_* siblings, which do fuzzy/partial matching.

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

Usage Guidelines4/5

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

Gives clear operative guidance: request the full prefix, and if an expected part is missing, look under its own prefix. It also explains the include_dns conditional. It stops short of naming sibling tools (e.g. search_components_by_refdes) as alternatives for partial matches, so it earns a 4 rather than a 5.

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