Skip to main content
Glama

component_add

Destructive

Adds a logical component to a Proteus project using the current expected_revision, without drawing it on the schematic.

Instructions

Add a logical component; does NOT draw in Proteus. Use current expected_revision.

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": {
      "project": "<project>",
      "expected_revision": "<expected_revision>",
      "ref": "<ref>",
      "device": "<device>",
      "position": "<position>"
    },
    "name": "component_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes
deviceYes
mirrorNo
projectYes
positionYes
rotationNo
propertiesNo
library_pathNo
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is documented structurally. The description adds real value by clarifying the operation is logical/model-level only and does not render in Proteus, plus the expected_revision concurrency requirement, but it does not say what existing data may be overwritten, what errors occur on revision mismatch, or what the call returns.

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?

Two short sentences, zero filler, with the essential caveat ('does NOT draw in Proteus') front-loaded right after the purpose. The terseness is efficient but borders on cryptic for a 9-parameter tool.

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 destructive, 9-parameter mutation tool with no parameter descriptions and no output schema, the description is far too thin. An agent knows the rough purpose and the revision requirement but not how to build required arguments or what state changes result.

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 description coverage is 0% across 9 parameters with 5 required, so the schema provides no semantic help. The description only touches 'expected_revision' and leaves ref, device, position, rotation, mirror, library_path, and properties entirely unexplained, including whether 'ref' must be unique or how library_path interacts with device lookup.

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 logical component') and adds the crucial negative qualifier 'does NOT draw in Proteus', which separates it from anything that renders or edits live output. It does not explicitly name a sibling like component_set or native_set_component, so differentiation is left partly to inference.

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?

'Use current expected_revision' gives a clear prerequisite for calling it, implying optimistic-concurrency usage. However, there is no when-to-use vs. when-not guidance relative to the many sibling mutation tools, and no statement of what to do on a stale revision.

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