Skip to main content
Glama
Sign In
KiCad MCP Server

KiCad MCP Server

by brovk2008
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

lock_track

Lock or unlock a track segment in a PCB layout to prevent accidental modification.

Instructions

Lock or unlock a track segment.

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": {
      "track_id": "<track_id>",
      "locked": "<locked>"
    },
    "name": "lock_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
lockedYes
track_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It fails to explain what locking a track entails (e.g., prevents editing, affects routing), whether it is reversible, or any side effects.

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 a single sentence, concise and front-loaded. However, it may be too brief for the necessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool (2 required params, no output schema, no annotations), the description is incomplete. It omits parameter usage, behavioral details, and context among many sibling lock tools.

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

Parameters2/5

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

The description does not explain the parameters beyond the schema. With 0% schema description coverage, it should clarify the 'locked' boolean (true=lock, false=unlock) and the 'track_id' string (which track?), but it does not.

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?

The description clearly states the action ('Lock or unlock') and the resource ('track segment'), differentiating it from sibling lock tools for other entities (e.g., lock_dimension, lock_footprint).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, no prerequisites, and no context on whether locking is a toggle or separate commands for lock vs unlock.

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