Skip to main content
Glama

component_set

Destructive

Update a component's logical properties, placement, rotation, or mirroring in a Proteus project and mark its native status as not applied.

Instructions

Update logical properties or placement; native status becomes not_applied.

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

Input Schema

NameRequiredDescriptionDefault
refYes
mirrorNo
projectYes
positionNo
rotationNo
propertiesYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 write/destructive nature is covered. The description does add one genuinely useful behavioral fact beyond the annotations: that the component's native status is reset to not_applied after the update. It does not explain what is lost, whether the change is reversible, or why expected_revision is required for concurrency.

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?

A single compact sentence with the operation front-loaded and zero filler. It is arguably over-compressed for a 7-parameter destructive tool, but there is no wasted wording to cut.

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, 7-parameter mutation with nested 'properties', no output schema, and 0% schema description coverage, the description is far too thin. It omits the meaning of the required revision guard, the accepted property keys, and the coordinate/rotation conventions.

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 7 parameters, so the description must compensate and largely fails to. 'Logical properties or placement' loosely gestures at 'properties' and 'position' but says nothing about 'ref', 'project', 'expected_revision' (a concurrency token), 'mirror', or 'rotation', all of which an agent must guess at from bare type definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Update' plus the objects 'logical properties or placement' gives a workable sense of the operation, but it never distinguishes this from siblings such as native_set_component or component_add, which plausibly touch the same component state. An agent cannot tell from the description alone which of these to pick.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus another tool, no prerequisites, and no exclusions. The only usage-adjacent information is a side effect ('native status becomes not_applied'), which hints at a consequence rather than a selection rule.

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