Skip to main content
Glama

Create GLSL shader

create_glsl_shader

Create a GLSL TOP in TouchDesigner with custom fragment and vertex shaders, bind numeric uniforms, and set output resolution.

Instructions

Create a GLSL TOP under parent_path that renders a custom fragment shader (and optional vertex shader). Caller shader source requires TDMCP_RAW_PYTHON=on and TDMCP_BRIDGE_ALLOW_EXEC=1. The shader source is placed in companion Text DATs (<name>_frag and, if given, <name>_vert) and wired to the GLSL TOP's pixel/vertex parameters; numeric uniforms are best-effort bound on the Vectors page and the output resolution is set. Returns the GLSL TOP path, the fragment/vertex DAT paths, and any warnings (e.g. sampler2D uniforms or uniform binds that need manual wiring).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName for the GLSL TOP (default 'glsl1').
uniformsNoOptional uniform declarations to best-effort bind on the GLSL TOP.
resolutionNoOutput resolution: '720p' (1280x720), '1080p' (1920x1080), '4K' (3840x2160), or 'input' (default — inherit from the input TOP).input
parent_pathYesParent COMP to create the GLSL TOP inside.
vertex_shaderNoOptional GLSL vertex shader source.
fragment_shaderYesGLSL fragment (pixel) shader source.
Behavior5/5

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

Despite annotations already indicating a non-read-only, non-destructive action, the description adds crucial context: required TDMCP settings, creation of companion Text DATs, wiring to GLSL TOP parameters, best-effort uniform binding, and manual wiring needs for sampler2D. No contradiction with 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?

Four sentences, each dense with information: purpose, prerequisites, behavior, and return values. No redundancy or filler. Exceptionally efficient.

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 creation tool with no output schema, the description thoroughly covers prerequisites, side effects, and return values (path, DAT paths, warnings). It fully equips the agent to understand what will happen and what to expect, even mentioning edge cases like sampler2D manual wiring.

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

Parameters4/5

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

Schema covers 100% of parameters, but the description adds integration semantics beyond the schema—e.g., numeric uniforms bind to the Vectors page, sampler2D maps to TOP input and requires manual wiring, and resolution is set. This enhances understanding of how parameters affect the output.

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 'Create a GLSL TOP under parent_path that renders a custom fragment shader' with specific verb and resource, distinguishing it from sibling tools like create_glsl_material or apply_glsl_top_mapping.

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. It describes the action but omits exclusions or alternative tool recommendations, which is a gap given the large sibling set.

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