Skip to main content
Glama

fillet_tracks

Rounds square PCB track corners in one change, keeps corners square where arcs would break clearance, reports skipped corners, and leaves locked tracks untouched.

Instructions

Round the square corners of tracks as ONE change. A corner stays square where the arc would break clearance; the answer counts those with reasons. Locked tracks are left alone; straighten_tracks undoes it.

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

Input Schema

NameRequiredDescriptionDefault
idsNoDefault every track
fileYesCircuit file
radiusNomm; default the rules' fillet radius

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses atomic single-change/undo semantics, that corners failing clearance stay square rather than erroring, that the response reports skipped corners with reasons, and that locked tracks are skipped. Missing only specifics on failure modes when the file or ids are invalid.

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?

Dense and front-loaded: the operation, the partial-application rule, and the undo path each get one clause with no filler. 'The answer counts those with reasons' is slightly compressed phrasing that costs a moment of parsing.

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 3-parameter mutation tool with no annotations and no output schema, the description covers the important unknowns: atomicity, partial application, locked-item behavior, and reversibility, and it sketches what the response reports. Only input-validation edge cases are unaddressed.

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 100%, so the schema already documents ids, file, and radius including defaults. The description adds no per-parameter meaning such as radius interaction with clearance, leaving parameter semantics at baseline.

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 and resource ('Round the square corners of tracks') plus a scope qualifier ('as ONE change'), which distinguishes it from the sibling straighten_tracks named later in the text. An agent can identify the operation without opening the schema.

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?

Names the inverse operation (straighten_tracks) and states a constraint (locked tracks are left alone), giving clear selection context. It stops short of explicit 'use this when...' framing, but the routing information is present.

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