Skip to main content
Glama
GaNotchVFX

touchbridge

by GaNotchVFX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

par_get

Retrieve parameter values from a TouchDesigner operator path, with optional glob filtering and detail control (summary, minimal).

Instructions

Read parameter values, optionally filtered by glob.

path (<class 'str'>): Operator path.

pattern (str | None): Glob like 't[xyz]'; None = all.

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
patternNo
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/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden — and it delivers: it discloses the read-only nature, the detail-level behaviors ('summary (long lists cut to 25 + count)', 'minimal (top-level scalars only)') and the token-cost trade-off of yaml vs json. For a non-destructive read tool this is solid behavioral disclosure, though return structure and error handling are not addressed.

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?

Purpose is front-loaded in the first line, followed by a clean parameter-per-line layout. The parameter documentation is long, but it earns its place — with 0% schema coverage it is the only parameter documentation the agent sees. No filler, no redundancy.

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 read tool with 4 params, zero schema descriptions, no annotations, and no output schema, the description covers purpose, filtering, all parameter semantics, and response formats. Gaps are the return payload structure and error behavior, which are minor for a pure read operation given everything else is specified.

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%, and the description fully compensates by documenting all four parameters inline with types, defaults, and rich semantics: glob pattern syntax with an example ('t[xyz]'), each detail mode's exact behavior, and the yaml/json format trade-off. Nothing about the parameters is left 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?

'Read parameter values, optionally filtered by glob' states a specific verb (read) and resource (parameter values) with a distinguishing filter mechanism. However, among siblings (par_get_all, par_info, par_set_expression) the description doesn't explicitly differentiate par_get from par_get_all, leaving an agent to infer the scope boundary from the glob filter rather than being told.

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

Usage Guidelines3/5

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

The glob parameter ('None = all') and the detail modes imply usage context, and mentioning 'yaml (default, token-cheap)' gives a mild selection hint. But the description never states when to prefer par_get over par_get_all or par_info, nor when not to use it. The guidance is implied, not explicit.

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