osc-bridge

find_presets

Read-onlyIdempotent

Search what SynthHub users shared (CC BY-SA 4.0): sounds, sequences, kits, projects, banks, MIDI clips. Filter by device, kind, category, genre, tag, author (pseudonym) or words; sort by newest, most stars, most loaded into a device or most trusted (confirmed on real devices). Returns, per preset, its id, name, kind, device, description, author, version, whether it has device data, settings, a MIDI file or an audio preview (URL), and its counts. Get one with get_preset.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_presets"
  }
}

Input Schema

Name	Required	Description
`tag`	No
`kind`	No
`sort`	No	new (default), most stars, most loaded into a device, or most confirmed on real devices.
`genre`	No
`limit`	No	At most this many (default 20).
`query`	No	Words that must all appear in the name, description, tags, genres, category or device id ('dx7 piano').
`author`	No	An author's pseudonym (e.g. 'u1a2b3c4d').
`device`	No	Driver id or slug (its other variants are included).
`offset`	No	Skip this many: the next page (the reply's total says how many match).
`user_id`	No	Your anonymous SynthHub id, if you kept it from an earlier session (see the server instructions). Optional.
`category`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026

changedInput schema / properties / sort / description

Previous value: -"Default new."New value: +"new (default), most stars, most loaded into a device, or most confirmed on real devices."

changedInput schema / properties / sort / enum

Previous value: -[
-  "new",
-  "popular",
-  "trusted"
-]New value: +[
+  "new",
+  "stars",
+  "loads",
+  "trusted"
+]

Changed2 schema fields changedOct 24, 2026

addedInput schema / properties / offset

Added value: +{
+  "description": "Skip this many: the next page (the reply's total says how many match).",
+  "minimum": 0,
+  "type": "integer"
+}

changedInput schema / properties / query / description

Previous value: -"Words that must all appear in the name, description, tags, genres or category."New value: +"Words that must all appear in the name, description, tags, genres, category or device id ('dx7 piano')."

Changed6 schema fields changedOct 23, 2026

addedInput schema / properties / author

Added value: +{
+  "description": "An author's pseudonym (e.g. 'u1a2b3c4d').",
+  "type": "string"
+}

addedInput schema / properties / category

Added value: +{
+  "enum": [
+    "bass",
+    "lead",
+    "pad",
+    "pluck",
+    "keys",
+    "organ",
+    "brass",
+    "strings",
+    "bell",
+    "arp",
+    "sequence",
+    "drums",
+    "percussion",
+    "fx",
+    "texture",
+    "vocal",
+    "other"
+  ],
+  "type": "string"
+}

addedInput schema / properties / genre
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / kind

Added value: +{
+  "enum": [
+    "sound",
+    "sequence",
+    "kit",
+    "project",
+    "bank",
+    "clip"
+  ],
+  "type": "string"
+}

changedInput schema / properties / query / description

Previous value: -"Words that must all appear in the name, description or tags."New value: +"Words that must all appear in the name, description, tags, genres or category."

addedInput schema / properties / sort

Added value: +{
+  "description": "Default new.",
+  "enum": [
+    "new",
+    "popular",
+    "trusted"
+  ],
+  "type": "string"
+}

AddedOct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds real context beyond that: the CC BY-SA 4.0 licensing of shared content, the meaning of the 'trusted' sort (confirmed on real devices), and exactly which fields come back per preset - none of which the annotations convey.

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?

Two dense sentences plus a three-word routing pointer, with the search scope front-loaded and no filler. The long return-field enumeration earns its space because no output schema exists to carry that information.

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

Completeness4/5

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

For an 11-parameter, zero-required discovery tool with no output schema, the description supplies the filter/sort surface and the per-preset return fields, so an agent can call it and interpret results. Only pagination mechanics are left to the offset/limit schema descriptions.

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 64%, and the description compensates by mapping the filter surface one-to-one onto parameters and clarifying semantics the schema omits: author is a pseudonym, 'trusted' means confirmed on real devices, and 'loaded into a device' defines the loads sort. It leaves the enum-only filters (kind, category, tag, genre) implicit, but those are self-describing enums.

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?

States a specific verb (Search) plus a precisely scoped resource (presets shared by SynthHub users), and enumerates the content kinds covered: sounds, sequences, kits, projects, banks, MIDI clips. It also routes single-item retrieval to get_preset, so an agent can tell it apart from that sibling without opening either schema.

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?

It clearly implies the discovery context: a filterable, sortable list search - and explicitly says 'Get one with get_preset' for single-item retrieval. It does not name alternatives such as preset_collection or explain when not to use it, but the selection context is unambiguous.

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.