Skip to main content
Glama
Sign In
tdmcp

tdmcp

by lucasmaher-hash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create simulation

create_simulation

Build GPU simulations in TouchDesigner—reaction-diffusion patterns, slime trails, or fluid advection—with adjustable decay for trail persistence.

Instructions

Build a GPU simulation: 'reaction_diffusion' grows Gray-Scott patterns (via the validated recipe), while 'slime' and 'fluid' run a feedback loop displaced by an evolving noise flow field — drifting trails and advected smears. Exposes a Decay knob (trail persistence). For more procedural techniques (cellular automata, flow fields, strange attractors) see create_generative_art.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_simulation"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoreaction_diffusion = Gray-Scott patterns (uses the validated recipe); slime = drifting decaying trails; fluid = advected smear.reaction_diffusion
decayNo(slime/fluid) Trail persistence — higher holds longer.
speedNo(slime/fluid) How fast the flow field evolves.
parent_pathNoParent COMP path the self-contained simulation container is created inside./project1
expose_controlsNo(slime/fluid) Expose a live 'Decay' knob bound to the gain Level TOP.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.1

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already indicate this is a mutating (readOnlyHint=false) and non-destructive tool. The description adds context about the visual behavior (e.g., noise-displaced feedback loops) but does not disclose operational details such as container creation in parent_path or whether existing content is overwritten. It provides modest behavioral enrichment beyond the annotations, warranting a mid-range score.

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?

Two sentences contain all essential information: the tool's function, the three variants with behavioral descriptions, one key control, and an explicit pointer to an alternative. There is no waste, and the critical details are front-loaded.

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?

Given the 100% schema coverage and adequate annotations, the description is largely complete for the agent to invoke the tool correctly. It covers the core purpose, variant behaviors, and an alternative path. It does not describe the return value or where the container is placed, but those are either in the schema or not critical for a build tool with no output schema, so the overall context is strong.

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% with detailed descriptions for every parameter, so the baseline is 3. The description repurposes some schema content (e.g., 'trail persistence' for decay) and adds minor conceptual depth (the noise flow field mechanism), but it does not significantly enhance understanding beyond what the schema already states. No parameter information is left undocumented.

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 uses a specific verb ('Build') and resource ('GPU simulation'), then enumerates three distinct simulation types with concrete visual outcomes (Gray-Scott patterns, drifting trails, advected smears). It also explicitly references an alternative tool ('create_generative_art') for other procedural techniques, clearly distinguishing its scope.

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

Usage Guidelines5/5

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

The first sentence establishes when to use this tool (to build GPU simulations of the listed types). The final sentence provides an explicit 'when-not' by directing the agent to create_generative_art for cellular automata, flow fields, and strange attractors. This is a clear, direct alternative with no ambiguity.

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