Skip to main content
Glama
Sign In

osc-bridge

by io.github.roomi-fields
OverviewDiscussionsAdmin

claim_presets

Idempotent

Claim presets SynthHub imported from another site (their page says 'imported', with the author's name and page there) when the user is that author: give the id of one of them; the server answers with a code for the user to add to their author page at that site (profile or bio). Once it is there, call again with verify: true: every preset imported from that author becomes the user's, to edit or withdraw.

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

Input Schema

NameRequiredDescriptionDefault
idYesId of one of the imported presets.
verifyNoTrue once the code is on the author page.
user_idNoYour anonymous SynthHub id, if you kept it from an earlier session (see the server instructions). Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already disclose readOnlyHint=false, idempotentHint=true, and openWorldHint=true, but the description adds the crucial external-side effect: the server returns a code the user must place on their page at the other site, and the verify call transfers every preset from that author, which become editable or withdrawable. That is real behavioral context beyond the annotations, though repeat-safety is only implied rather than stated.

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?

Dense but purposeful: the first clause establishes the precondition, the middle the code exchange, the end the verify outcome. It is a single long sentence with nested colons that is slightly hard to parse, but almost no word is wasted.

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

Completeness5/5

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

For a multi-step, cross-site ownership transfer with no output schema, the description covers the precondition, the intermediate artifact (code), where to place it, and the final effect on ownership. Nothing an agent needs to sequence the calls correctly is missing.

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 100%, so the baseline is 3, but the description adds semantic meaning for the two key parameters: id is 'one of the imported presets' and verify means 'once the code is on the author page'. That clarifies the state transition the flag controls, which the schema alone does not.

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 (claim) and resource (presets imported from another site) plus the precondition (the user is the original author). This is clearly distinct from siblings such as withdraw_preset, load_preset, or update_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?

Spells out the exact two-step procedure: first call with just the id to get a verification code, place it on the author page, then call again with verify: true. It also names the condition that selects this tool (the user is the author of the imported presets), leaving no inference needed.

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