Skip to main content
Glama

pcb_trim_extend_track

Trim or extend a PCB track endpoint along its existing line by projecting it toward a target point, keeping the track collinear and the opposite end fixed.

Instructions

Trim or extend one track endpoint along the track's own slope.

Finds the track endpoint nearest (from_x, from_y), then slides it to the perpendicular projection of (to_x, to_y) onto that track's line. The track stays collinear (no bend introduced) and the opposite end stays put, so this cleanly lengthens a track up to a target or pulls it back. All coordinates in mils.

Args: from_x, from_y: Picks which endpoint moves (nearest one wins). to_x, to_y: Target the moving end is projected toward. tolerance_mils: How close (from_x, from_y) must be to a real endpoint (default 5).

Returns: {"moved_end", "old_x", "old_y", "new_x", "new_y", "layer"}.

Input Schema

NameRequiredDescriptionDefault
to_xYes
to_yYes
from_xYes
from_yYes
tolerance_milsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries full burden and does well: it discloses that the opposite end stays put, that no bend is introduced, that the endpoint is chosen by nearest-match, and the mils unit. It omits failure behavior when no endpoint is within tolerance and any undo/permission notes, keeping it below 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.

Conciseness4/5

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

Purpose is front-loaded, followed by mechanics, then Args and Returns sections. Well organized; slightly verbose in the mechanics paragraph but every sentence conveys behavior an agent needs.

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?

A geometry mutation tool with an output schema present, so return values are doubly covered. The description supplies units, endpoint-selection logic, and the return shape. Missing only edge-case/failure handling for a mutation with no annotations.

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

Parameters5/5

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

Schema coverage is 0%, so the description must compensate and does: every parameter is explained (from/to semantics, the nearest-wins rule, and tolerance_mils meaning plus default 5). This fully compensates for the empty schema descriptions.

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?

States a specific verb (trim or extend) on a specific resource (one track endpoint) along the track's own slope. This is clearly distinguishable from siblings like pcb_place_tracks or pcb_cleanup_tracks without opening any schema.

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?

Explains the mechanics and effect (collinear lengthen/pull-back) which implies when it is useful, but never names alternatives (e.g. pcb_cleanup_tracks, pcb_set_track_width) or states explicit when-not conditions. Usage context is implied rather than routed.

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