Skip to main content
Glama
pcb-agent-mcp

pcb-agent-mcp

tool_search

Search PCB design, calculation, and EDA tools by keyword query; returns up to a specified number of matching results for selecting the right operation.

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

Input Schema

NameRequiredDescriptionDefault
limitNo ...
queryYes ...

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 disclosing behavior, and it discloses nothing — no read/write semantics, no result format, no ranking, pagination, or scope behavior. The only signal is the required 'query' parameter and a 'limit' default of 8, which the description never explains.

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 only content is an ellipsis placeholder, which is under-specification rather than conciseness. There is no front-loaded statement of purpose and no structure an agent can parse.

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 two-parameter search tool with no annotations and no output schema, the description should at minimum state what corpus is searched and what results look like. It provides none of this, leaving the required 'query' parameter's expected content entirely unexplained.

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 reported at 100%, so both 'query' and 'limit' are already documented in the schema and the description is not required to compensate. Per the coverage rule, the baseline is 3, and the description neither adds nor detracts from parameter meaning.

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 an empty placeholder (" ..."), so it states nothing about what the tool does. The name tool_search hints at searching tools, but sibling names such as part_search and tool_call make that inference unreliable, and the description itself supplies no verb or resource.

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 guidance at all about when to use this tool, when not to, or how it differs from part_search or tool_call. An agent has no textual basis for choosing between these similarly named tools.

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