Skip to main content
Glama

fit_board

Define a PCB board area from parts, dimensions, or an outline, set 2 or 4 copper layers, and identify any components left outside.

Instructions

Set the board as ONE change: by default a rectangle round the parts plus margin; or width and height (centred on x, y), or an outline; layers: 2 or 4 copper layers. The answer names parts left outside.

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": {
      "file": "<file>"
    },
    "name": "fit_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoCentre; default the board's
yNo
fileYesCircuit file
widthNomm, with height: this rectangle
heightNo
layersNo
marginNomm; default 2
outlineNoCorners in mm

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/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. It discloses one useful behavioral fact — the response reports parts left outside the board — and that all geometry changes happen as a single operation. It says nothing about what happens to an existing board outline, whether the change is reversible, or permission/precondition requirements for a mutation tool.

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?

It is short and front-loaded with the main operation, but the clipped, semicolon-chained style ('or width and height (centred on x, y), or an outline') and the dangling sentence about the answer make it denser than it needs to be. A slightly longer structured sentence would read more reliably.

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

Completeness3/5

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

For an 8-parameter mutation tool with no annotations and no output schema, the description covers the main modes and the notable return information (parts outside). It leaves gaps around mode precedence, units for coordinates, and the effect on a pre-existing board, which are meaningful for correct invocation.

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 63%, and the description does add real meaning: width pairs with height to form a rectangle centred on x/y, outline is an alternative to that rectangle, margin has a default of 2, and layers is restricted to 2 or 4. It does not resolve precedence when outline and width/height are both given, and units for x/y are not stated in the description.

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 concrete verb and resource: it sets the board shape (rectangle from parts + margin, explicit width/height, or outline) and the copper layer count (2 or 4). That distinguishes it from siblings like import_board and board_summary, though the telegraphic phrasing ('Set the board as ONE change') takes a second read.

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?

It does convey the default mode (rectangle around the parts plus margin) and the two alternative modes, which is implicit guidance on which parameters to choose. It never says when to prefer this over import_board or how it interacts with autoplace/autoroute, so guidance stops at mode selection.

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