Skip to main content
Glama

autoplace

Places PCB parts by their connections in one change, including unplaced or selected parts while keeping locked parts fixed, and can grow the board to fit before autorouting.

Instructions

Place parts by their connections as ONE change: every part without a position, or only some parts or one instance. Placed and locked parts stay. Run it before autoroute. With fit: true a part with no room grows the board. The answer gives wire length, board size, overlaps, parts with no room and copper a move left behind.

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

Input Schema

NameRequiredDescriptionDefault
fitNoAlso fit the board round the parts
fileYesCircuit file
partsNoe.g. ["U1"]
instanceNoe.g. "PS1"
connectorsNolast (default): connectors after the rest; ahead: each just before the part it serves
budgetSecondsNoDefault 20

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Without annotations, the description still discloses important behavior: placement happens as one change, locked/placed parts are preserved, fit can grow the board, and the result reports wire length, board size, overlaps, unplaced parts, and leftover copper. It does not cover reversibility or permissions, but the main mutation and side-effect profile is clear.

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

Conciseness4/5

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

The description is front-loaded with the core action and avoids unnecessary repetition. The final return-value list is dense and slightly awkward in wording, but overall the text earns its place.

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?

For a six-parameter mutating placement tool with no annotations and no output schema, the description covers the key behavior, sequencing guidance, fit side effect, and output summary. Some details such as budget or connector semantics remain in the schema, but the description is complete enough to call correctly.

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 already 100%, so the schema carries most parameter meaning. The description still adds useful semantics beyond the schema, especially that fit: true can grow the board when a part has no room, and it clarifies that parts may be all missing parts, a subset, or one instance.

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

Purpose5/5

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

The description states a specific verb and resource: place parts by their connections. It clarifies the scope as every unpositioned part, a subset of parts, or one instance, and distinguishes the step from autoroute by saying to run it before autoroute.

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?

It gives clear usage context: run before autoroute, target parts without positions or named subsets/instances, and placed or locked parts stay put. It does not explicitly state when not to use it, but the placement scope and sequencing guidance are sufficient for an agent.

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