Skip to main content
Glama
awdr74100

figwright

by awdr74100
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bind_component_property

Attach a declared component property to a sublayer field so it drives visibility, text, or instance swap. Pass null to remove that field's binding.

Instructions

Attach a declared component property (from add_component_property) to a sublayer field so it drives that layer: field "visible" for a BOOLEAN, "characters" for a TEXT (the node must be a TEXT node), "mainComponent" for an INSTANCE_SWAP (the node must be an INSTANCE). The same property can be bound to several layers (call once per layer). Pass propertyId: null to remove the binding on that field. The property's type must match the field and it must exist on the containing component. Returns { ok, nodeId }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldYesWhich layer field the property drives
nodeIdYesSublayer inside the component to bind on
propertyIdYesProperty id (name#id) to bind, or null to unbind this field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.0
    • removedInput schema / properties / propertyId / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / propertyId / type
      Added value: +[
+  "string",
+  "null"
+]
  2. Changed1 schema field changedv0.1.3
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Addedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only cover readOnlyHint=false and destructiveHint=false, so the description carries most of the burden and delivers: the same property can bind to several layers (idempotency/scope), propertyId: null removes the binding on that field, and the return shape is { ok, nodeId }. It does not cover failure/error behavior or permission needs.

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?

It is a single dense paragraph, but the core action is front-loaded and each clause (field/type mapping, multi-layer note, null-unbind, return value) carries information. Slightly packed with embedded constraints, but no filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter mutation tool with no output schema, the description supplies the missing return shape, the unbind path, the type-matching preconditions, and the multi-binding model. An agent has everything needed to invoke 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 100%, giving a baseline of 3. The description goes beyond the schema by mapping each enum value to a required property type and node type (BOOLEAN→visible, TEXT→characters on a TEXT node, INSTANCE_SWAP→mainComponent on an INSTANCE), which is genuinely useful disambiguation rather than repetition.

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

Purpose5/5

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

The description states a precise verb+resource: attaching a declared component property to a sublayer field so it drives that layer. It anchors the tool against its sibling add_component_property (which declares the property) and implies the inverse of delete_component_property, so an agent can distinguish it without opening the schema.

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

Usage Guidelines4/5

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

It gives clear precondition context: the property must come from add_component_property, must exist on the containing component, and its type must match the target field/node type. It explains the per-layer call model (call once per layer). It stops short of naming an explicit alternative or when-not condition versus sibling binding tools such as bind_variable_to_node.

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