Skip to main content
Glama

Manage TouchDesigner community packages

manage_packages
Destructive

Search, list, inspect, install, or uninstall TouchDesigner community packages. Dry-run by default; stages under ~/.tdmcp/packages without running third-party scripts.

Instructions

Search, list, inspect, doctor, dry-run install, stage, and uninstall manifest-driven TouchDesigner community packages. Dry-run is the default. Installs stage packages under ~/.tdmcp/packages and only import into TouchDesigner when the bridge is reachable and the package has a safe .tox import path. This tool never runs third-party scripts, pip installs, model downloads, or external app setup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesPackage-manager action to run.
package_idNoPackage id or alias, e.g. 'mediapipe', 'raytk', or 'shader-park-td'.
queryNoSearch query for action='search'.
installedNoFor action='list', include installed state.
dry_runNoFor action='install', plan safely without downloading or mutating by default.
project_pathNoTouchDesigner project COMP for optional live import./project1
nameNoOptional custom TD node name for live import.
pinNoOptional Git ref/tag to stage instead of the manifest default.
yesNoAllow replacement of existing staged files / TD package target when applicable.
allow_python_depsNoAcknowledge optional Python dependency guidance; does not run pip.
allow_externalNoAcknowledge optional external dependency guidance; does not configure apps/services.
packages_rootNoAdvanced override for package state/cache root. Defaults to ~/.tdmcp/packages.
Behavior4/5

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

The description adds important behavioral context beyond annotations: dry-run default, staging location, import conditions, and explicit statements about not running third-party scripts. This informs safe usage without contradicting the annotations.

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?

Three sentences, front-loaded with actions, each sentence adds value. No wasted words, and the structure is logical.

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

Completeness3/5

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

Given the complexity (12 parameters, multiple actions, no output schema), the description provides essential safety and behavior context but lacks explanations for each action (e.g., what 'doctor' does). The schema compensates for parameter details, but action semantics are assumed.

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

Parameters3/5

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

Schema coverage is 100%, so the baseline is 3. The description does not add additional parameter details beyond what the schema provides, but it does reinforce the dry-run default, which is already in 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 clearly states the tool manages TouchDesigner community packages with specific verbs (search, list, inspect, doctor, install, uninstall, stage) and distinguishes from sibling tools like 'install_library_package' by specifying 'community packages'.

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?

No explicit guidance on when to use this tool versus alternatives. While the actions are listed, there is no comparison to similar tools (e.g., 'install_library_package') or when to avoid using it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pantani/tdmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server