Skip to main content
Glama
Sign In
PCB Parts MCP Server

PCB Parts MCP Server

by Averyy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

PCB Design Rules

get_design_rules
Read-onlyIdempotent

Retrieve curated PCB design rules for power, protection, interfaces, MCUs, layout, and EMC by topic, keyword, or exact file key; leave topic empty to list all rule files.

Instructions

Curated PCB design rules for power, protection, interfaces, MCUs, layout and EMC. An empty topic lists every rule file. note says the files were found by their text, not their name or keywords.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_design_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoExact returned key (e.g., "power/ldo", "INDEX.md") or keyword matched against category/filename and common terms (e.g., "ldo", "usb", "type-c", "lipo", "stm32g0"); otherwise the files that discuss it most (e.g., "boot mode")

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.21

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description adds genuine behavioral context beyond that: an empty topic returns the full index, and results are matched against file text rather than filenames or keywords, which sets correct expectations about surprising hits.

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

Conciseness3/5

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

The first sentence is well front-loaded and dense with useful scope. The second sentence, 'note says the files were found by their text, not their name or keywords', is a lower-case fragment with an unclear referent ('note'), so brevity comes at the cost of readability.

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?

An output schema exists, annotations are rich, and there is a single optional parameter, so the description's job is small and it mostly covers it: purpose, empty-input behavior, and the matching caveat. Only the contrast with sibling search tools is left implicit.

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 the baseline is 3. The description reinforces the empty-string default (lists every rule file), which is the one behavior the schema does not spell out, but it adds nothing on key format or how ranking works when a keyword yields a weak match.

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?

The description names a concrete resource (curated PCB design rules) and enumerates its coverage domains: power, protection, interfaces, MCUs, layout and EMC. It also states the empty-topic behavior. It does not explicitly contrast with siblings such as board_search, but 'curated rule text' is clearly a different artifact from board/part search.

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?

Usage is implied: pass a topic key or keyword, or leave empty to list every rule file. There is no explicit statement of when to prefer this over board_search or cse_search, nor any exclusion guidance, so the agent must infer that this is for design-rule reference rather than board lookup.

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

Deploy Server

Other Tools