Skip to main content
Glama
GaNotchVFX

touchbridge

by GaNotchVFX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

layout_align

Align TouchDesigner nodes along horizontal or vertical axis, setting start position and spacing between centers.

Instructions

Distribute nodes along a horizontal or vertical axis.

paths (list[str]): Ordered operator paths.

axis (str | None): 'horizontal' (default) or 'vertical'.

start_x (float | None): X of the first node.

start_y (float | None): Y of the first node.

spacing (float | None): Gap between centres (default 200).

detail (str | None): full (default) | summary (long lists cut to 25 + count) | minimal (top-level scalars only).

response_format (str | None): yaml (default, token-cheap) | json.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
axisNo
pathsYes
detailNo
spacingNo
start_xNo
start_yNo
response_formatNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.0
    • addedInput schema / properties / detail
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Detail"
+}
    • addedInput schema / properties / response_format
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Response Format"
+}
  2. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the operation and output formatting options (detail, response_format) but does not explicitly state that this mutates node positions, whether the operation is reversible, or if specific permissions are required. This is a notable gap for a layout-modifying tool.

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?

The description is efficient: a one-line purpose followed by a line per parameter. It front-loads the main function and avoids unnecessary prose, making it scannable and easy to parse.

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

Completeness4/5

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

For a tool with 7 parameters and no output schema, the description covers the core operation and parameter semantics well. It hints at output via response_format and detail but does not describe the actual response structure or whether the operation is silent or returns a summary. The absence of side-effect disclosure is a minor gap, given the mutation nature.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must define every parameter. It does so thoroughly: 'paths' clarifies they are ordered operator paths, 'axis' gives allowed values and default, 'spacing' explains the gap and default, and detail/response_format document all options. This fully compensates for the schema's lack of descriptions.

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 opens with a clear, specific verb and resource: 'Distribute nodes along a horizontal or vertical axis.' This distinguishes it from sibling tools like layout_set_position (which positions a single node) and node_* tools. The axis specification further narrows the scope.

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 description does not provide any guidance on when to use this tool versus alternatives. It only describes the operation and parameters, with no mention of use cases, exclusions, or prerequisites such as 'use layout_set_position for single-node positioning.' An agent must infer the appropriate context solely from the name and sibling list.

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