Skip to main content
Glama

search_parts_registry

Search an open KiCad parts registry without login. Matches each query word against a part's ID, name, family, category, manufacturer and keywords, so you can find the exact component to add to your project.

Instructions

Search an open registry of KiCad parts (no login).

The tool compares the query with the ID, the name, the family, the category, the manufacturer and the keywords of each part. Example queries: "usb c connector", "0402 capacitor", "nrf9151".

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

Input Schema

NameRequiredDescriptionDefault
limitNoThe maximum number of results (default 20).
queryYesThe words to find. Each word must match. "*" is a wildcard.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

It explicitly mentions a crucial operational behavior: 'no login' is required, which impacts execution requirements. Listing the indexed fields (ID, name, family, etc.) also provides behavioral context.

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 highly efficient and well-structured. It front-loads critical information (no login, search fields) before moving to practical examples.

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?

For a straightforward search operation, the definition is highly complete. It covers scope, access requirements, and query behavior, leaving no immediate gaps for a calling agent.

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?

The description adds significant semantic value by stating that each word in the query must match, defining the search logic. The concrete examples are vital for understanding practical input usage.

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 identifies the resource (KiCad parts registry) and the specific action (search). It provides high clarity by detailing the six fields used for matching queries.

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 helps by providing concrete query examples, guiding the agent on the intended search format. It lacks explicit statements on when to choose this over similar sibling search tools.

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