Skip to main content
Glama
the-real-talk

the-real-talk

set_component_property_reference

Link a text node's characters or any node's visibility inside a component to a component property by propertyId, enabling dynamic component variants.

Instructions

Link a text node (characters) or any node (visible) inside a component to a component property, by propertyId.

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": {
      "nodeId": "<nodeId>",
      "field": "<field>",
      "propertyId": "<propertyId>"
    },
    "name": "set_component_property_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldYes
nodeIdYesID of the node inside the component
propertyIdYespropertyId returned by add_component_property

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it omits key behavior for a mutation: whether an existing binding is overwritten, whether the referenced property must already exist, and what happens for the unexplained 'mainComponent' value. It does add the useful constraint that the target node must live inside the component, which is the only real behavioral content.

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 front-loaded sentence with no padding. The parenthetical '(characters)' and '(visible)' are slightly clunky but each carries the node-type mapping, so nothing is wasteful.

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 write operation with no annotations and no output schema, the definition should describe the effect of the call and its failure modes. It leaves the agent guessing about overwrite semantics, property existence requirements, and the meaning of one of three enum values.

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 67% and the two documented parameters already say most of what the description says. The description does add meaning by explaining that 'characters' targets text nodes and 'visible' applies to any node, which the bare enum does not convey; however the third enum value 'mainComponent' is left completely unexplained.

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?

The description names a specific verb ('Link') and resource ('a text node or any node inside a component to a component property'), and it ties the enum values 'characters' and 'visible' to the node types they apply to. It stops short of distinguishing this from sibling mutation tools such as set_instance_properties or set_node_properties, but the core action is unambiguous.

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?

The phrase 'inside a component' implies a precondition, but the description never states when to use this tool versus editing a property or setting instance properties, nor does it say what must already exist (a component property created via add_component_property, a node that is a descendant of the component). No exclusions or alternatives are given.

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

Deploy Server

Other Tools