Skip to main content
Glama
Averyy

PCB Parts MCP Server

by Averyy

Search Components

jlc_search
Read-onlyIdempotent

Search electronic components with natural language queries and parametric filters to find in-stock parts for PCB design projects.

Instructions

Fast DB search with natural language parsing and parametric filters. In-stock parts only (stock >= 10).

Args: query: Search query - supports natural language like: - "10k resistor 0603 1%" (auto-detects type, value, package, tolerance) - "100nF 25V capacitor" (auto-applies voltage >= 25V filter) - "n-channel mosfet SOT-23" (auto-filters to MOSFETs subcategory) Or use with explicit filters for text search within results.

subcategory_id: Subcategory ID (e.g., 2954 for MOSFETs)
subcategory_name: Subcategory name (e.g., "MOSFETs", "Schottky Diodes")
spec_filters: Parametric filters for precise searches. Each filter is a dict:
    - name: Attribute name (Vgs(th), Capacitance, Voltage, etc.)
    - op: Operator: "=", ">=", "<=", ">", "<"
    - value: Value with units (e.g., "2.5V", "10uF", "20mΩ")
    Example: [{"name": "Vgs(th)", "op": "<", "value": "2.5V"}]

min_stock: Minimum stock (default 10). Database only indexes stock >= 10.
library_type: "basic", "preferred", "no_fee", "extended", or None (all)
prefer_no_fee: Sort basic/preferred first (default True)
package: Single package filter (e.g., "0603", "SOT-23")
packages: Multiple packages (OR logic): ["0402", "0603", "0805"]
manufacturer: Manufacturer filter
match_all_terms: AND logic for query terms (default True)
sort_by: "stock" (highest) or "price" (cheapest)
limit: Max results (default 50, max 100)

Attribute aliases: MOSFETs: Vgs(th), Vds, Id, Rds(on) Diodes: Vr, If, Vf Passives: Capacitance, Resistance, Inductance, Voltage, Tolerance

Returns: results: Matching components with specs total: Total count (before limit) filters_applied: Applied filters (useful for debugging) parsed: (when using natural language) What was extracted from query

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
subcategory_idNo
subcategory_nameNo
spec_filtersNo
min_stockNo
library_typeNo
prefer_no_feeNo
packageNo
packagesNo
manufacturerNo
match_all_termsNo
sort_byNostock
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

The description adds valuable behavioral context beyond annotations: it specifies that the search is limited to 'In-stock parts only (stock >= 10)' and 'Database only indexes stock >= 10', which are not covered by annotations like readOnlyHint. It also details natural language parsing capabilities and result sorting options. However, it does not mention rate limits or authentication needs, which could be relevant for a search tool.

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?

The description is well-structured with sections like 'Args:', 'Attribute aliases:', and 'Returns:', making it easy to navigate. It is appropriately sized for a tool with 13 parameters, but some parts (e.g., the detailed 'query' examples) could be slightly condensed without losing clarity. Overall, it is efficient but not maximally concise.

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

Completeness5/5

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

Given the complexity (13 parameters, 0% schema coverage) and the presence of an output schema (implied by 'Returns:' section), the description is complete. It thoroughly explains all parameters, provides usage examples, details return values, and adds behavioral context like stock limitations. No gaps are evident for a search tool of this nature.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by providing detailed explanations for all 13 parameters. It includes examples for 'query', clarifies defaults (e.g., 'min_stock: Minimum stock (default 10)'), lists enum values for 'library_type' and 'sort_by', and explains complex structures like 'spec_filters' with attribute aliases. This adds significant meaning beyond the bare schema.

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 clearly states the tool's purpose as 'Fast DB search with natural language parsing and parametric filters' and specifies 'In-stock parts only (stock >= 10)', which distinguishes it from other search tools. It provides specific details about what it searches (components) and how (natural language parsing, parametric filters), making it distinct from siblings like 'jlc_stock_check' or 'jlc_get_part'.

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?

The description provides clear context for when to use this tool: for searching components with natural language queries or parametric filters, and it specifies 'In-stock parts only (stock >= 10)'. However, it does not explicitly mention when not to use it or name alternatives among sibling tools (e.g., 'jlc_search_help' or 'jlc_find_alternatives'), which prevents a score of 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Averyy/pcbparts-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server