osc-bridge

update_preset

Publish a new version of a preset this account shared: new content (hex, file, settings or midi_file) makes a new version, kept with a change note — earlier versions stay available; the description fields alone change it in place. Someone else's preset: share yours with derived_from instead.

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": {
      "id": "<id>"
    },
    "name": "update_preset"
  }
}

Input Schema

Name	Required	Description
`id`	Yes
`hex`	No
`key`	No
`name`	No
`tags`	No
`tips`	No
`tempo`	No
`genres`	No
`user_id`	No	Your anonymous SynthHub id, if you kept it from an earlier session (see the server instructions). Optional.
`category`	No
`firmware`	No
`settings`	No
`changelog`	No	What changed in this version (500 characters at most).
`description`	No
`midi_base64`	No	A standard MIDI file, base64 (64 KB at most).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this as non-read-only, non-destructive, non-idempotent, and open-world. The description adds valuable behavioral detail beyond those annotations: content changes create a new version, earlier versions remain available, and a change note is kept. It does not fully explain ownership failure behavior or response shape, but it is substantially richer than the annotations alone.

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 two dense but purposeful sentences. The main behavior and sibling alternative are front-loaded, with no wasted filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 15-parameter mutation tool with no output schema and low schema coverage, the description covers the central versioning workflow well. However, it does not explain the return value or fully clarify parameter behavior, leaving an agent to infer too much from the schema alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 20% schema description coverage across 15 parameters, the description has to carry parameter meaning. It explains the important content-versus-metadata distinction, but only names a few content fields and uses a mismatched "file" / "midi_file" naming instead of the schema's midi_base64, while leaving many metadata parameters ambiguous.

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 and resource: "Publish a new version of a preset this account shared." It also distinguishes the core semantics of version creation versus in-place metadata edits and names the sibling tool to use for someone else's preset.

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?

It gives explicit guidance for the main case (your own shared preset) and the exception (someone else's preset), directing the agent to share_preset with derived_from instead. It also clarifies when new content creates a version versus when description fields alone update in place.

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

All osc-bridge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.