Skip to main content
Glama

import_graphic

Places an SVG or DXF logo or mark onto a specified PCB layer as one board change, with optional centering, width scaling, fill, and copper net assignment.

Instructions

Place a drawing (logo, mark) from source, a project .svg/.dxf, on the board as ONE change; kept in graphics/. Centre x,y and width in mm (else board centre); width keeps aspect; fill fills closed outlines; net (copper) makes it that net's copper. Answers id, size, omissions.

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>",
      "source": "<source>",
      "layer": "<layer>"
    },
    "name": "import_graphic"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
netNo
fileYes
fillNo
nameNo
layerYes
scaleNo
widthNo
sourceYes
rotationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations the description carries the load and does well: it discloses atomicity ('as ONE change'), storage destination ('kept in graphics/'), coordinate/width defaults ('else board centre', 'width keeps aspect'), and fill/net effects. It omits permissions, error handling, and idempotency, keeping it short of a 5.

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?

Front-loaded with purpose and efficiently dense, every clause adding a behavior; the telegraphic semicolon style is compact but slightly reduces readability.

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 an 11-param tool with no output schema it covers most behaviors and hints at the return ('Answers id, size, omissions'), though it leaves layer, rotation, scale, and name semantics unexplained.

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 0%, so the description must compensate; it explains x,y (centre), width (mm, keeps aspect), fill, net (copper), and source, but says nothing about name, scale, rotation, file, or the layer enum values — several of 11 params remain undocumented.

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 ('Place') and resource ('a drawing (logo, mark) ... .svg/.dxf ... on the board'), and clarifies the outcome ('as ONE change; kept in graphics/'), which clearly sets it apart from board/part import siblings.

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

Usage Guidelines3/5

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

Constrains the input ('a project .svg/.dxf') which implies when it applies, but gives no explicit when-to-use versus alternatives or when-not guidance.

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