Skip to main content
Glama

straighten_tracks

Restores square corners to rounded tracks in one change where clearance allows; locked tracks remain unchanged.

Instructions

Put back the square corners fillet_tracks rounded, as ONE change, where clearance allows. Locked tracks are left alone.

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

Input Schema

NameRequiredDescriptionDefault
idsNoDefault every track
fileYesCircuit file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 the full burden and does well: it discloses atomicity ('as ONE change'), a clearance constraint, and that locked tracks are skipped rather than modified. It omits what the return or failure behavior looks like when clearance blocks a corner, but covers the key mutation semantics.

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

Conciseness5/5

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

Two sentences, front-loaded with the action and immediately followed by the operational constraints. Every phrase ('ONE change', 'where clearance allows', 'Locked tracks') carries behavioral information.

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 two-parameter mutation tool with no annotations or output schema, the description covers scope, atomicity, clearance, and lock handling. The main residual gap is failure/return behavior if a corner cannot be straightened, which is minor for this tool's complexity.

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 100%, with both parameters documented ('ids' defaults to every track; 'file' is the circuit file). The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 gives a specific inverse operation ('Put back the square corners fillet_tracks rounded') and explicitly names the sibling it reverses. An agent can distinguish this from fillet_tracks without opening either 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?

It establishes the inverse relationship to fillet_tracks and states the operational condition ('where clearance allows') plus an exclusion ('Locked tracks are left alone'). It does not spell out when-not-to-use or what to do if clearance fails, but the applicable context is clear.

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