Skip to main content
Glama
GaNotchVFX

touchbridge

by GaNotchVFX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

node_get

Retrieve complete metadata for a TouchDesigner operator, including parameters, connections, and position. Choose detail level and output format to fit your workflow.

Instructions

Full metadata for one operator (params, connections, position).

path (<class 'str'>): Full path of the operator.

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
pathYes
detailNo
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

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and it does explain meaningful output behavior: long lists are truncated to 25 + count for summary, minimal returns top-level scalars, and YAML is the token-cheap default. It stops short of error behavior for invalid paths, but the main behavior of a read-only metadata getter is disclosed.

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 core purpose is the first sentence, followed by three compact parameter definitions with no filler. Every line adds information needed to call the tool.

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?

Given there is no output schema or annotations, the description covers the required path, the output detail levels, and the response format, which is enough to invoke it correctly. An explicit example or missing-path error note would make it fully complete, but they are not critical for this simple getter.

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?

The schema has 0% property descriptions, and the inline parameter notes fully compensate: path is explained, detail lists all three modes with defaults and truncation semantics, and response_format explains the default and cost implications. This goes well beyond the bare anyOf/string schema.

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 names the exact resource ('one operator') and the returned contents (metadata with params, connections, position), making it a specific single-node lookup rather than a list or search. This is enough to pick it apart from node_list and par_get.

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 explicit statement about when to use node_get versus node_list, node_find, or par_get, and no when-not-to-use conditions. The singular wording implies a lookup case, but the selection context is left entirely to inference.

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