Skip to main content
Glama
Sign In

osc-bridge

by io.github.roomi-fields
OverviewDiscussionsAdmin

report_preset

Idempotent

Tell SynthHub how a shared preset behaved once loaded on a real device: 'works' (it loaded and sounds as described), 'fails' (refused, wrong sound), or 'factory' (it is a factory preset or someone else's sound: presets that several users flag are hidden until reviewed). Give the firmware.

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>",
      "outcome": "<outcome>"
    },
    "name": "report_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
noteNoWhat happened, briefly (500 characters at most).
outcomeYes
user_idNoYour anonymous SynthHub id, if you kept it from an earlier session (see the server instructions). Optional.
firmwareNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations declare this is a non-destructive, idempotent write, and the description adds real context beyond that: it discloses the consequence that presets flagged by several users are hidden until reviewed. That consequence is valuable for an agent to understand the impact of the 'factory' outcome, though the write/report flow could be clarified further.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the opening clause, and each clause adds useful content (outcome definitions, flagging consequence). The parenthetical elaborations make it somewhat dense, but no sentence is wasted.

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 moderate-complexity reporting tool with annotations and no output schema, the description covers purpose, outcome semantics, the firmware requirement, and the downstream flagging effect. Remaining gaps (id meaning, note usage) are minor and largely addressed by the schema.

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?

With only 40% schema coverage, the description does meaningful compensating work: it explains the semantic meaning of the three 'outcome' values and tells the agent to supply 'firmware'. Combined with schema-level descriptions for 'note' and 'user_id', most parameters are covered, though 'id' is left unexplained in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Tell SynthHub') and a precise resource ('how a shared preset behaved once loaded on a real device'), and it breaks the report into three defined outcomes. It is unmistakable what the tool does, though it doesn't name or contrast sibling report tools like report_result or report_mapping.

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?

The phrase 'once loaded on a real device' establishes the trigger condition for calling it, and 'Give the firmware' is an explicit instruction. However, there are no explicit exclusions or pointers to alternative tools (e.g. report_result), so routing between similar report tools is left to inference.

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

All osc-bridge toolsInspect
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.

Resources