osc-bridge

set_profile

Idempotent

Set the public profile shown on this account's author page and with its shared presets and comments, instead of its pseudonym alone: display name, link (https), a few words, the presets put first, where they are, more links, their instruments and a README. A field left out stays as it is; an empty one is cleared. Ask the user what they want shown; all of it is public.

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": "set_profile"
  }
}

Input Schema

Name	Required	Description
`bio`	No	A few words about them and their sounds, 600 characters at most.
`gear`	No	The instruments they play, e.g. 'Korg minilogue'.
`link`	No	An https:// address: their site, SoundCloud, Bandcamp…
`name`	No	40 characters at most.
`about`	No	Their README in Markdown: who they are, how they work, what they offer; 8000 characters at most.
`links`	No	More https:// pages of theirs: a channel, a shop, a band.
`user_id`	No	Your anonymous SynthHub id, if you kept it from an earlier session (see the server instructions). Optional.
`featured`	No	Ids of their own listed presets, shown first on their page, in this order.
`location`	No	Where they make music, 60 characters at most.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 25, 2026

addedInput schema / properties / about

Added value: +{
+  "description": "Their README in Markdown: who they are, how they work, what they offer; 8000 characters at most.",
+  "type": "string"
+}

addedInput schema / properties / gear

Added value: +{
+  "description": "The instruments they play, e.g. 'Korg minilogue'.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

addedInput schema / properties / links

Added value: +{
+  "description": "More https:// pages of theirs: a channel, a shop, a band.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 8,
+  "type": "array"
+}

addedInput schema / properties / location

Added value: +{
+  "description": "Where they make music, 60 characters at most.",
+  "type": "string"
+}

Changed2 schema fields changedOct 24, 2026

addedInput schema / properties / bio

Added value: +{
+  "description": "A few words about them and their sounds, 600 characters at most.",
+  "type": "string"
+}

addedInput schema / properties / featured

Added value: +{
+  "description": "Ids of their own listed presets, shown first on their page, in this order.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 6,
+  "type": "array"
+}

AddedOct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The annotations already state this is a non-read-only, non-destructive, idempotent operation, and the description adds important behavior beyond them: omitted fields remain unchanged, empty fields are cleared, and everything set is public. It does not describe auth requirements, errors, or what a successful call returns, so it stops short of the top score.

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 three sentences, front-loads the purpose, then covers update semantics and public visibility. The field list is dense but useful for recognizing the profile scope, and every sentence contributes to correct invocation.

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 a nine-parameter optional-field profile update with no output schema, the description covers the key context: public visibility, partial updates, clearing, and user consent. It could add a note about auth or success behavior, but the annotations and schema already carry much of that load.

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 description coverage is 100%, so the schema already documents the nine parameters, including length limits and https requirements. The description adds meaningful semantics by explaining partial-update behavior: omitted fields stay as-is and empty fields are cleared.

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 states a specific verb and resource: setting this account's public author-page profile, including where it appears with shared presets and comments. It distinguishes the profile from the pseudonym alone and makes the scope concrete enough for an agent to select it for profile-management tasks.

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 gives clear situational guidance by saying to ask the user what they want shown and warning that all fields are public. It does not name explicit alternatives or exclusions, but no sibling tool appears to be a direct substitute for setting a public profile.

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.