Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

part_search

Search electronic parts by query across online and offline sources with paging controls and timeouts, returning matching components so you can select parts for PCB designs without manual catalog lookups.

Instructions

...

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

Input Schema

NameRequiredDescriptionDefault
pageNo ...
pathNo ...
limitNo ...
queryYes ...
sourceNo ...
timeout_sNo ...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.43

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It does not say whether lookups hit a network index or a local cache, how the 'source' modes differ in behavior, whether results are paginated, or what failures look like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The body is an empty placeholder rather than prose; this is under-specification, not conciseness. There is no front-loaded statement of intent, so nothing earns its place because nothing is there.

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

Completeness1/5

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

For a 6-parameter search tool with no annotations and no output schema, the description should at minimum explain what is searched, what the source modes mean, and what is returned. None of that is present, so an agent must infer the tool's entire contract from the schema alone.

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 description coverage is 100% with 6 documented parameters, including an enum on 'source', so the schema itself is doing all the semantic work. The description adds no syntax, format, or interaction detail (e.g., how 'path' constrains scope relative to 'query') beyond what the schema already provides, which matches the baseline for high-coverage schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a literal placeholder (" ...") and states no verb, resource, or scope. The name 'part_search' hints at searching for parts, but the definition itself conveys nothing an agent can act on, and nothing distinguishes it from the sibling 'part_get' or 'tool_search'.

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

Usage Guidelines1/5

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

There is no when-to-use, when-not-to-use, or alternative-routing guidance of any kind. An agent cannot tell from this definition whether part_search is for fuzzy lookup, exact match, or online/offline retrieval, nor when to prefer part_get.

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