Skip to main content
Glama
Nivakaran-S

eda-agent

by Nivakaran-S
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pcb_get_pad_properties

Retrieve PCB pad properties filtered by net or component designator, including shape, size, hole, thermal relief, and solder/paste mask expansion. Provide a filter to avoid returning all pads.

Instructions

Get detailed pad information filtered by net or component.

Returns pad shape, size, hole, thermal relief, and solder/paste mask expansion details. Provide at least one filter (net or designator) to avoid returning all pads on the board.

Args: net: Filter by net name (e.g., "GND", "VCC"). Optional. designator: Filter by component designator (e.g., "U1"). Optional.

Returns: Dictionary with "pads" array (each with name, component, x, y, net, layer, shape, top_x_size, top_y_size, hole_size, rotation, is_smd, solder_mask_expansion, solder_mask_bottom_expansion, solder_mask_separate, paste_mask_expansion) and "count". solder_mask_expansion is the TOP side when solder_mask_separate is true and both sides when it is false; the bottom value is stored either way and takes effect once the sides are unlinked. Expansions read 0 when the pad follows the board's rule.

Input Schema

NameRequiredDescriptionDefault
netNo
designatorNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does so reasonably: it discloses the returned field set, the unbounded-query hazard, and the non-obvious semantics of solder_mask_expansion (top side when separate is true, both sides otherwise, zero when following board rules). It does not mention permissions, read-only nature, or performance/limits, so not a 5.

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 core guidance is front-loaded in the first sentence, which is good, but a large share of the body restates return fields already covered by the output schema. The mask-expansion caveat is worth keeping; the field enumeration largely is not.

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 two-parameter read tool with an output schema, nothing an agent needs to call it correctly is missing: filter requirement, return shape, and the one genuinely confusing field semantic are all covered. The remaining verbosity is redundancy, not a gap.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it does: it defines both parameters, gives concrete value examples ("GND", "VCC", "U1"), marks them optional, and explains they act as filters. It stops short of describing interaction between the two filters (AND/OR) or default empty-string behavior.

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 (get pad properties) and scopes it to filtering by net or component, which is clear. It does not name the nearest sibling (pcb_get_component_pads or lib_get_pad_geometry), so an agent has to infer the distinction rather than being told.

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?

Explicitly directs the caller to supply at least one filter and explains the consequence of omitting it (returns all pads on the board). That is real usage guidance rather than a restated name. It lacks any when-to-use-this-vs-sibling routing, which keeps it below a 5.

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