Adds a synthesizer module to an existing VCV Rack patch, specifying plugin name, model, and optional rack position.
Add a module to an existing patch
| Name | Required | Description | Default |
|---|---|---|---|
| model | Yes | Module model name (e.g., 'VCO', 'VCF') | |
| plugin | Yes | Plugin name (e.g., 'Fundamental', 'Bogaudio') | |
| filepath | Yes | Path to the .vcv patch file | |
| position_x | No | X position in rack units (optional) | |
| position_y | No | Y position (row, usually 0) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description lacks disclosure of behavioral traits such as what happens if the module already exists, if the filepath is invalid, or any side effects. This leaves the agent underinformed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single concise sentence that communicates the core purpose without any wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has 5 parameters and no output schema, yet the description does not explain what the function returns, error conditions, or success indicators. It is incomplete for an agent to invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 no additional meaning beyond the schema's parameter descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Add' and resource 'module to an existing patch', distinguishing it from siblings like 'create_patch' or 'connect_modules'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for adding a module to an existing patch but offers no explicit guidance on when to use this tool versus alternatives like 'modify_parameter' or 'list_modules'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/minimaltek/cardinal-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server