Skip to main content
Glama

Plecs Layout Check

plecs_layout_check
Read-only

Checks schematic geometry in an open PLECS model, reporting overlapping component boxes, diagonal wire segments, and wires crossing components to flag layout readability issues.

Instructions

Check schematic geometry of a model that is open in PLECS.

Uses the bounding box per component from plecs.webserver getCircuitBitmap plus Position/Points from the .plecs text, and reports only what is certain: LAYOUT-001 (error) two component boxes intersect, LAYOUT-002 (warning) a wire polyline has a diagonal segment, LAYOUT-003 (info) a wire is drawn across a component that is not one of its endpoints, LAYOUT-004 (info) a polar two-terminal part has terminal 1 on the wrong side for reading order (horizontal: left, vertical: top) and carries the exact direction / flipped to apply. Orientation is opt-in (include_orientation=True): it is a house style, and roughly two thirds of the bundled demos do not follow it. A crossing is cosmetic - PLECS connects only through explicit connections - but it makes the schematic hard to read.

Top-level schematic only; margin absorbs the ~2 unit rounding between schematic coordinates and rendered pixels.

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": {
      "model_name": "<model_name>"
    },
    "name": "plecs_layout_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
marginNo
model_nameYes
include_wiresNo
include_orientationNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.4
    • addedInput schema / properties / include_orientation
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
  2. First observedv0.4.1

TDQS

A3.9/5.0
Behavior5/5

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

Despite readOnlyHint=true being supplied, the description adds substantial behavioral context: the data sources (getCircuitBitmap bounding boxes plus .plecs Position/Points), severity of each code, that a crossing is cosmetic because PLECS only connects explicitly, and that orientation findings are house-style and disabled by default. This is exactly the kind of extra context annotations cannot convey.

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?

Purpose and code list are front-loaded, and nearly every sentence carries information (diagnostic meanings, data provenance, crossing semantics, margin purpose). It is somewhat dense and could tighten the orientation/crossing sentences, but there is no filler.

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, so return structure needn't be described, and the code semantics plus 'top-level only' and margin caveat give an agent enough to invoke correctly. The one gap is the undisclosed behavior of include_wires, which is neither in the schema nor the description.

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 0%, so the description must carry all four parameters. It explains margin (absorbs ~2 units of coordinate/rendering rounding) and include_orientation (opt-in, default off, with rationale), but leaves include_wires and model_name unaddressed beyond implication, so roughly half the parameters are explained.

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 ('Check schematic geometry of a model that is open in PLECS') and enumerates the exact diagnostics it produces (LAYOUT-001 through LAYOUT-004). It does not name or differentiate itself from sibling checkers like plecs_check, plecs_validate, or plecs_diagnose, which keeps it from a 5 even though the geometry scope is distinctive.

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?

The description implies its use case (layout/readability review of an open top-level schematic) and notes orientation is opt-in via include_orientation with the caveat that two thirds of demos don't follow the house style. It never says when to prefer this over plecs_validate or plecs_check, nor states exclusions beyond 'top-level schematic only'.

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