Skip to main content
Glama

Edit shader live loop

edit_shader_live_loop
Destructive

Update GLSL shader source in a DAT, replace specific text, and get immediate error checks with an optional preview image to validate the visual result.

Instructions

Edit a GLSL/Text DAT and immediately run the practical shader feedback loop: write or surgically replace source text, inspect the shader/output node for errors, and optionally capture a compact inline preview. Uses set_dat_content/edit_dat_content under the hood so DAT write guardrails stay consistent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoset overwrites the shader DAT; replace performs a surgical text replacement.set
dat_pathYesAbsolute path to the GLSL/Text DAT to edit.
error_pathNoNode to inspect for errors after the edit. Defaults to preview_path, then dat_path.
new_stringNoReplacement text. Required when mode is replace.
old_stringNoSubstring to find. Required when mode is replace.
replace_allNoFor replace mode, replace all matches instead of requiring exactly one match.
shader_codeNoFull shader source. Required when mode is set.
jpeg_qualityNoJPEG quality.
parent_depthNoUpstream depth for inline-preview error inspection.
preview_pathNoTOP path to preview after the shader edit, usually the GLSL TOP output or Null TOP.
preview_widthNoPreview width.
preview_formatNoPreview encoding.jpeg
preview_heightNoPreview height.
include_previewNoCapture a compact inline preview after editing when preview_path is supplied.
recursive_errorsNoIf true, check errors recursively under error_path.
Behavior4/5

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

Annotations flag readOnly=false and destructive=true, and the description aligns by describing write/replace actions. It adds value by disclosing that the tool immediately runs the feedback loop, inspects errors, and can produce a preview, plus mentions DAT write guardrails.

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, each adding value: purpose, workflow, and implementation detail. No redundancy or filler.

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 tool with 15 parameters and no output schema, the description provides a strong mental model of the workflow, including edit, inspect, and preview. It doesn't explicitly state the return structure, but the preview mention hints at output, making it reasonably complete.

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 coverage is 100%, so the baseline is 3. The description adds meaning by framing parameters like mode ('write or surgically replace'), the error inspection workflow, and the compact inline preview, which helps connect parameters to the tool's purpose.

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 edits a GLSL/Text DAT and runs a shader feedback loop including error inspection and optional preview. This distinguishes it from generic DAT editing tools like edit_dat_content and set_dat_content by emphasizing the shader-specific workflow.

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

Usage Guidelines4/5

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

The description implies usage for shader editing with immediate feedback and mentions the underlying set_dat_content/edit_dat_content functions, providing context on delegation. However, it doesn't explicitly state when not to use this tool or name direct alternatives for non-shader DAT editing.

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/lucasmaher-hash/touch-designer-mcp'

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