Space Dust MCP

Overview Schema Source Related Servers Discussions Admin

create_preset

Create a new synth preset from an existing one or Init, apply parameter changes, and save it safely without overwriting.

Instructions

Create a new preset and save it to the user's preset folder.

changes maps parameter ids to values written the way the plugin shows them —
{"filterCutoff": "260", "osc1Waveform": "Saw", "subOscOn": "on"}.

based_on is the preset to start from; "Init" starts from the synth's default state.
Starting from an existing preset the user likes is usually the better move.

Refuses to overwrite an existing preset — pick another name, or use adjust_preset.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "changes": "<changes>"
    },
    "name": "create_preset"
  }
}

Input Schema

Name	Required	Default
`name`	Yes
`note`	No
`changes`	Yes
`based_on`	No	Init

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

A4.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it reveals the save location, the changes mapping format with an example, the based_on default and semantics, and the overwrite refusal. It does not cover potential errors for invalid parameter values or permissions, but the core behavioral traits are transparent.

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?

The description is front-loaded with the main purpose and each paragraph adds necessary detail—the changes example, based_on guidance, and overwrite warning. No filler or 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 tool with 4 parameters, nested objects, and no annotations, the description is remarkably complete. It explains the two complex parameters, the failure mode, and the alternative action. An output schema exists, so return values need not be described.

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?

Despite schema coverage being 0%, the description adds substantial meaning for 'changes' (format and example) and 'based_on' (default and guidance). 'name' and 'note' are left to the schema, but they are simple and self-explanatory.

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 new preset and save it to the user's preset folder,' specifying a concrete verb and resource. It distinguishes itself from sibling tools by explicitly noting it refuses to overwrite and pointing to adjust_preset as the alternative for that action.

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 description gives explicit when-to-use guidance: 'Starting from an existing preset the user likes is usually the better move.' It also provides a clear when-not-to-use and an alternative: 'Refuses to overwrite an existing preset — pick another name, or use adjust_preset.'

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server