Skip to main content
Glama
flaco-source

altium-mcp

by flaco-source

Edit schematic sheet

edit_schematic
Destructive

Edit Altium schematic sheets: move or rotate components, update parameters, and add text, wires, buses, and power ports.

Instructions

Purpose: Edit one schematic sheet (.SchDoc) via a single tool with multiple modes (action).

When to use: Move or rotate symbols, set parameters, place components, add text/net labels, wires, buses, bus entries. After editing, call get_schematic_data on the same sheet to verify.

Sheet targeting (required): Provide schematic_full_path (absolute .SchDoc, preferred) OR schematic_sheet_file_name (file name only, e.g. Sheet1.SchDoc) with project_full_path or Altium focused project.

Common parameters: action (string), schematic_full_path?, project_full_path?, schematic_sheet_file_name?

Actions:

  • set_component_transform — designator (required); optional x_mils, y_mils, rotation_deg (at least one of position/rotation must be set). Coordinates in mils; rotation in degrees (snapped to 0/90/180/270).

  • set_component_parameters — designator (required); parameter_names[] and parameter_values[] (same length; updates existing parameters or adds new ones).

  • place_component — lib_reference, designator, x_mils, y_mils, rotation_deg (optional, default 0); sch_library_path (absolute .SchLib) strongly required for a real symbol. Without sch_library_path the bridge only creates an empty schematic component shell (designator + LibReference, no library graphics—pins/body do not appear). With sch_library_path the bridge uses PlaceSchComponent from that file. All coordinates are sheet mils in the same space as get_schematic_data schematic_x/schematic_y; place inside the white drawing area (use existing objects on the sheet as reference, typically thousands of mils, not pixel-scale values).

  • add_text — text, x_mils, y_mils (free string on sheet).

  • add_net_label — net_name, x_mils, y_mils; optional rotation_deg.

  • place_net_label — alias of add_net_label (response echoes the action you sent).

  • add_wire — wire_points_csv: comma-separated mils pairs for orthogonal polyline segments, e.g. "0,0,1000,0,1000,500" creates (0,0)-(1000,0) and (1000,0)-(1000,500).

  • place_wire — alias of add_wire.

  • add_bus — same wire_points_csv format as add_wire; creates bus segments (eBus) instead of wires.

  • add_bus_entry — wire_points_csv must be exactly four numbers x1,y1,x2,y2 (mils) for one bus-entry segment (eBusEntry).

  • place_power_port — power_port_style (required): circle | arrow | bar | wave | gnd_power | power_ground | gnd_signal | signal_ground | gnd_earth | earth; x_mils, y_mils; optional net_name (defaults by style: GND for ground styles, VCC for supply styles), rotation_deg, show_net_name (default true).

  • place_gnd — same coordinates; optional power_port_style (default gnd_power in bridge), optional net_name (default GND if empty).

  • place_vcc — same coordinates; optional power_port_style (default arrow in bridge), optional net_name (default VCC if empty).

Returns: Bridge JSON result object with action, sheet, details (mode-specific). On Delphi-side failure, error text may start with ERROR: (e.g. COMPONENT_NOT_FOUND, SHEET_REQUIRED).

Prerequisites: Target .SchDoc must belong to an open project. Bridge command schematic_edit.

Notes: Does not auto-save the document unless the user saves in Altium. API behavior may vary slightly by AD major version. Wires and buses use straight segments (Location–Corner per segment). Delphi errors for buses include FACTORY_BUS_FAILED, BUS_POINTS_CSV_REQUIRED, FACTORY_BUS_ENTRY_FAILED, BUS_ENTRY_POINTS_NEED_EXACTLY_FOUR_NUMBERS, BUS_ENTRY_POINTS_CSV_REQUIRED. Power ports (ISch_PowerObject): POWER_PORT_STYLE_REQUIRED, POWER_PORT_STYLE_INVALID, FACTORY_POWER_OBJECT_FAILED, X_Y_MILS_REQUIRED.

Debugging / freezes: If the Altium Script IDE has a breakpoint set in Altium_API or schematic_edit (or Run with debugger), the script stops before writing response.json and the MCP client will see TIMEOUT. Clear all breakpoints, use Run without debugging, or press Continue/Stop Debugging in Altium. After a TIMEOUT, if no later tool runs, delete .bridge.lock in the MCP workspace folder so the next call is not blocked by the lock wait.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNo
actionYes
x_milsNo
y_milsNo
net_nameNo
designatorNo
rotation_degNo
lib_referenceNo
show_net_nameNo
parameter_namesNo
wire_points_csvNo
parameter_valuesNo
power_port_styleNo
sch_library_pathNo
project_full_pathNo
schematic_full_pathNo
schematic_sheet_file_nameNo
Behavior5/5

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

The description goes far beyond the minimal annotations (readOnlyHint=false, destructiveHint=true) by disclosing that it does not auto-save, that errors may start with 'ERROR:', that breakpoints in Altium can cause TIMEOUT and require lock file deletion, and that some actions create empty component shells without a library path. This gives the agent a rich understanding of side effects and failure modes.

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 long but well-structured with clear headings (Purpose, When to use, Sheet targeting, Actions, Returns, Prerequisites, Notes, Debugging). Every section contributes necessary detail for the tool's 17 parameters and 13 actions; however, the length itself is a slight burden for an agent to parse, so it is not maximally concise.

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

Completeness5/5

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

Given the tool has 17 parameters, no output schema, and complex action-specific behavior, the description is remarkably complete. It covers return format ('Bridge JSON result object with action, sheet, details'), prerequisites, error prefixes, Delphi-side error codes, and debugging/lock handling, leaving minimal ambiguity for an agent.

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?

The schema has 0% description coverage, but the description fully compensates. It explains coordinate units (mils), rotation snapping (0/90/180/270), the exact CSV format for wires and buses (e.g., '0,0,1000,0,1000,500'), required vs optional parameters per action, and power_port_style enum values with default net names.

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 opens with 'Edit one schematic sheet (.SchDoc) via a single tool with multiple modes (action)', clearly stating the verb, resource, and scope. It enumerates concrete actions (move, rotate, set parameters, place components, add text/net labels/wires/buses) that distinguish it from read-only siblings like get_schematic_data.

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?

The 'When to use' section explicitly lists the editing scenarios and instructs to 'call get_schematic_data on the same sheet to verify' after editing, providing a clear workflow and an alternative read tool. It also states prerequisites (target .SchDoc must belong to an open project), though it does not explicitly state when NOT to use the tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/flaco-source/altium-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server