Skip to main content
Glama

set_props

Set or add literal properties on a PCB part—such as placement coordinates, rotation, resistance, footprint, label offsets, no-connect pins, and supplier part numbers—and use null to remove them.

Instructions

Set literal props of a part (pcbX, pcbY, pcbRotation, schX, resistance, footprint, …); missing props are added. schNameAt, schValueAt and pcbNameAt are label offsets { x, y }; noConnect: "pin3,pin10" flags pins meant to stay open; supplierPartNumbers: "jlcpcb:C25804". null removes these.

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>",
      "part": "<part>",
      "props": "<props>"
    },
    "name": "set_props"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesCircuit file
partYesPart name, e.g. R1
propsYese.g. { "pcbX": 4, "resistance": "10k" }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does reasonably well: it discloses upsert behavior ('missing props are added'), removal semantics ('null removes these'), and the special meaning of label-offset props. It omits permission requirements, error behavior for unknown parts, and whether setting props is reversible.

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?

Dense and front-loaded: the core action leads, followed by per-prop syntax notes with zero filler. The semicolon-chained style is terse but scannable; no sentence is wasted.

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 mutation tool with no annotations and no output schema, the description covers the risky semantics well: adding missing props, deleting via null, and the polymorphic value forms. The remaining gaps are its relation to set_part_fields and what happens when file/part does not exist.

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

Parameters4/5

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

Schema description coverage is 100% and the nested props object is already typed, so the baseline would be 3. The description earns above baseline by explaining what the schema cannot: that schNameAt/schValueAt/pcbNameAt are {x,y} offsets, the concrete noConnect string format, and the supplierPartNumbers 'jlcpcb:C25804' form, plus that null deletes.

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?

A specific verb ('Set') and resource ('literal props of a part') with concrete prop examples (pcbX, resistance, footprint) and an explicit upsert note ('missing props are added'). It is clear what the tool does, but it never differentiates itself from the sibling set_part_fields, which sounds closely related.

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?

Usage is implied through prop examples and special-case syntax (label offsets, noConnect, supplierPartNumbers), which suggests when particular forms apply. There is no explicit when-to-use vs when-not guidance and no mention of the obvious alternative set_part_fields.

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