recommend_changes
Analyze your current music project against a target style and generate an EditPlan with proposed changes across tempo, key, harmony, instrumentation, and mastering, each with a clear reason.
Instructions
Diff the current project against a target fingerprint and return an EditPlan — a list of ProposedEdit{target, action, reason, params} across the v1 dimensions (tempo, key, harmony, instrumentation, mastering-match), each annotated with a human-readable reason. Read-only: surface these reasons to the user for approval, THEN call apply_changes. Includes honest caveats (detection confidence, taste calls).
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": {
"target_style": "<target_style>"
},
"name": "recommend_changes"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| target_style | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| intent | Yes | e.g. "make this sound Classical". | |
| target_style | No | ||
| edits | No | ||
| caveats | No | Honest limits — low detection confidence, taste-based choices, etc. |