Skip to main content
Glama
GaNotchVFX

touchbridge

by GaNotchVFX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

system_info

Retrieve TouchDesigner system details, including version, cook rate, realtime status, and registered methods, with configurable summary or full output.

Instructions

TD version, cook rate, realtime flag and the full registered method list.

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

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

With no annotations, the description carries the behavior burden. It discloses that summary truncates long lists to 25 entries plus a count and that yaml is token-cheap, which are genuinely useful behavioral traits. It does not explicitly state read-only/no side effects, but the informational content makes that reasonably clear.

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 three compact lines with no filler; the return content is front-loaded and each parameter line earns its place by defining behavior. It is easy to scan and act on.

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 zero-required-parameter read tool with no output schema, the description covers the return fields and all parameter variations needed to invoke it correctly. There are no obvious missing pieces for an agent to call it.

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%, yet the description fully documents both parameters, including allowed values, defaults, and effects. This is high-value semantic information that the input schema alone does not provide.

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 exactly what is returned: TD version, cook rate, realtime flag, and the full registered method list. This is specific enough to distinguish system_info from siblings such as system_ping and bridge_status without needing 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 Guidelines3/5

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

No alternative tools or explicit 'use this when' guidance is provided, so the routing context is only implied by the name and output list. The detail and response_format lines do give useful guidance for selecting parameter modes, which lifts it above a complete absence of usage direction.

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