Skip to main content
Glama
Sign In

PCBEditor

by com.pcbeditor
OverviewDiscussionsAdmin

Search parts and footprints

search_parts
Read-onlyIdempotent

Searches PCBEditor's verified parts and footprint library, with pin maps. Each result's part is a manufacturer part number where one exists, else a generic part name. A connector search also lists matching footprints.

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

Input Schema

NameRequiredDescriptionDefault
kindNoWhat to search (default part).
limitNoHow many (1-40, default 10).
queryYesA part number, part family or description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the library is curated/'verified', and results carry pin maps plus MPN-or-generic naming, which tells the agent what to expect in the payload.

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?

Three short sentences, front-loaded with the core action, and each adds a distinct fact (library scope, identifier semantics, connector footprint side-effect). Minor redundancy between the title phrase and the first sentence.

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 correctly fills the return-value gap by explaining identifier semantics and the presence of pin maps. It lacks matching/fuzzy-search behavior and result ordering, but is otherwise sufficient for a read-only, 3-parameter search tool.

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

Parameters3/5

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

Schema coverage is 100%, so query, kind and limit are all documented in the schema with defaults and ranges. The description only marginally extends this by noting connector searches also return footprints; it adds no syntax or matching-behavior detail for the query string. Baseline 3 applies.

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 ('Searches PCBEditor's verified parts and footprint library') and clarifies what a result's part identifier represents (manufacturer part number or generic name). It does not explicitly distinguish itself from the sibling get_part, which is the main gap.

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?

The note that 'a connector search also lists matching footprints' implies the kind-based behavior, but there is no explicit guidance on when to use this search versus get_part, list_inventory, or add_inventory_part. Usage must be inferred from the name and siblings.

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

All PCBEditor toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources