Skip to main content
Glama
GaNotchVFX

touchbridge

by GaNotchVFX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

project_versions

List saved TouchDesigner .toe versions in a project folder, newest-first. Choose summary or minimal detail to keep long lists readable.

Instructions

List saved .toe versions in the project folder, newest-first.

folder (str | None): Folder to scan (default project folder).

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
folderNo
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.3/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 burden. It discloses read-only listing, newest-first ordering, list truncation behavior in summary mode, and response format options. It does not explicitly state that no files are modified or mention auth prerequisites, but the 'list' verb and output-mode detail are transparent enough for this operation.

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 short, front-loaded with the core purpose, and uses a compact parameter reference format. Every sentence adds value, including the 'token-cheap' note on the yaml default.

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-only list tool with three simple optional parameters and no output schema, the description is largely complete. It explains what the tool does, how it orders results, and how detail and response formats affect the output, though it does not enumerate the exact fields returned within each detail mode.

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 fully compensates by explaining folder scanning scope, the three detail levels with their exact behaviors (full, summary with 25-item cutoff and count, minimal top-level scalars), and the response_format choices with defaults. Every parameter is given meaningful semantics beyond the 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 states a specific verb and resource: 'List saved .toe versions in the project folder, newest-first.' It clearly distinguishes this tool from siblings like project_snapshot or bridge_save_increment by focusing on reading existing version files rather than creating or restoring them.

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?

It gives context about defaults and optional modes, but it never explicitly says when to prefer this tool over a sibling or when not to use it. The implied usage is for inspecting saved project versions, yet no alternative or exclusion is mentioned.

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