Skip to main content
Glama
Sign In
KiCad MCP Server

KiCad MCP Server

by brovk2008
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

update_text_layer

Change the layer assignment of a text or text box in a PCB layout by specifying the text ID and target layer name.

Instructions

Update the layer of a text or text box item.

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": {
      "text_id": "<text_id>",
      "layer_name": "<layer_name>"
    },
    "name": "update_text_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
text_idYes
layer_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so description must disclose behaviors. It only says 'Update' implying mutation but does not mention side effects, error conditions, or requirements (e.g., permissions, layer existence).

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?

Single sentence with no fluff. Front-loaded with key verb and resource.

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 no output schema, two required params, and no annotations, the description fails to inform the agent about how to obtain text_id, where to find layer names, or what the tool returns. Incomplete for safe invocation.

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?

Schema coverage is 0%, yet description adds minimal meaning beyond parameter names. It does not explain what text_id refers to (ID of which text?) or valid layer_name values.

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 clearly states the action (Update) and the resource (layer of a text or text box item). It distinguishes from siblings like update_shape_layer by specifying 'text or text box'.

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 such as update_shape_layer. No prerequisites or context for usage are provided.

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