Skip to main content
Glama
j0KZ
by j0KZ

create_rack

Generate a complete Eurorack-style Pure Data rack from module specifications, with automatic wiring and MIDI controller configuration for hardware control.

Instructions

Generate an entire Eurorack-style rack of Pd patches at once. Takes an array of module specs (template + params) and generates: individual .pd files for each module + a combined _rack.pd with all modules side-by-side. Use wiring to connect modules via throw~/catch~ (audio) or send/receive (control) buses. Add controller config to map a MIDI controller (e.g. K2) to rack parameters — generates _controller.pd (MIDI routing) and _k2_config.json (LED feedback). Parameters auto-map by category (faders→volume, pots→filter) or use custom mappings. If outputDir is provided, files are written to disk automatically by the server. IMPORTANT: The complete .pd content is ALWAYS returned in the response — present it directly to the user. STOP after presenting the result. Do NOT run bash, ls, mkdir, cat, cp, mv, or ANY file/shell operations after this tool. Do NOT try to save, verify, or create files — everything is already handled. Just show the content to the user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modulesYesArray of module specifications. Each becomes a separate .pd file.
wiringNoInter-module connections for the combined _rack.pd patch.
controllerNoMIDI controller configuration. Generates _controller.pd (input) and/or _output_controller.pd (output) for hardware control of rack parameters.
outputDirNoOptional ABSOLUTE directory path to write all .pd files. If omitted, content is returned but not written to disk.
Behavior4/5

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

No annotations provided, so description bears full responsibility. It discloses that files are written to disk if outputDir is provided, that content is always returned, and warns against post-tool file operations. It could mention overwriting behavior, but overall transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately long but well-structured: main action first, then details on modules, wiring, controller, outputDir, and critical imperatives. Each sentence adds value; minimal redundancy.

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 complex tool with 4 parameters, nested objects, and no output schema, the description fully covers all aspects: purpose, parameter details, return behavior, and safety instructions. No gaps for agent decision-making.

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 baseline is 3. The description adds significant value beyond schema: explains wiring connections, controller auto-mapping, and outputDir behavior, making parameters more actionable.

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 it generates an entire Eurorack-style rack of Pd patches, listing specific outputs (individual .pd files and combined _rack.pd) and optional components (wiring, controller). It distinguishes from sibling tools like create_from_template by being a bulk generation tool.

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 includes explicit instructions on how to handle the output (present content to user, stop, avoid file operations), and outlines when to use wiring and controller config. While it doesn't explicitly compare to alternatives, the usage context is clear.

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/j0KZ/synthlab-mcp-server'

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