Skip to main content
Glama

place_part

Add a component to a circuit file by library part ID or built-in kind, assign a designator, and optionally set its schematic page and properties.

Instructions

Add a part to a circuit: a library part id from list_parts or a built-in kind (guide { topic: "writing-circuits" }).

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>",
      "name": "<name>"
    },
    "name": "place_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesCircuit file
nameYesNew designator, e.g. U2 or R5
pageNoSchematic page, made when missing; default "Main"
partYes
propsNoe.g. { "resistance": "10k" }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. "Add" implies mutation, but the description says nothing about permissions, duplicate designators, file/page creation side effects, or expected errors. It leaves the agent with only the bare action.

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?

A single front-loaded sentence with no wasted words. The alternative sources and guide reference are compactly integrated without bloating the definition.

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?

For a mutation tool with no annotations, no output schema, and a nested `props` object, the description is too thin. It explains part sourcing but omits behavioral details such as side effects, failure modes, or what the tool returns, leaving significant gaps for an agent to call it correctly.

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 coverage is 80%, so the baseline is 3. The description adds meaningful context for the otherwise undocumented `part` parameter by explaining that it can be a library id from list_parts or a built-in kind, which the schema does not state. It does not cover the other parameters, but the schema already documents them.

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?

States a specific verb and resource: "Add a part to a circuit." It also names where part identifiers come from (list_parts or a built-in kind), which helps distinguish it from list_parts. It does not explain how it differs from create_part or import_part, so sibling differentiation is only partial.

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?

The description implies when to use this tool by pointing to list_parts and a guide topic for building circuits. It gives no explicit exclusions or comparison to create_part/import_part, so the agent must infer that those tools serve different purposes.

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