Skip to main content
Glama
Sign In

osc-bridge

by io.github.roomi-fields
OverviewDiscussionsAdmin

link_account

Link this account to the user's SynthHub account on the site: returns a one-time address (valid 15 minutes) for the user to open and sign in (passkey, e-mail, Google or Discord). Afterwards what this account shared appears under their profile, and they manage it — and their stars, collections, comments — from the site. Offer it when the user wants to see or manage what you shared for them.

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

Input Schema

NameRequiredDescriptionDefault
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.4/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: it returns a one-time address valid for 15 minutes, the user signs in via passkey, e-mail, Google, or Discord, and afterward shared content appears under their profile. It also explains that the user manages stars, collections, and comments from the site. These details give the agent a complete mental model of what the call does and what follows.

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 description is front-loaded with the action and the immediate return value, then explains the lasting outcome and when to offer it. Every sentence contributes relevant information. It is a single dense paragraph rather than separated clauses, but it is not bloated.

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?

Because there is no output schema, the description must explain the return value, and it does: a one-time address valid for 15 minutes. It also explains the post-link side effects and the user-facing purpose, which is sufficient for an agent to decide when to call it. Nothing material is missing for this simple, single-parameter tool.

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

Parameters3/5

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

There is one optional parameter, and schema description coverage is 100%, so the schema fully documents user_id. The description does not mention the parameter at all, so it adds no meaning beyond the schema. Baseline 3 is appropriate when the schema already carries parameter semantics.

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: 'Link this account to the user's SynthHub account on the site.' It goes further by explaining the immediate result (a one-time address) and the lasting effect (shared content appears under the user's profile). No sibling tool does account linking, so the absence of sibling differentiation does not reduce clarity.

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 a clear when-to-use signal: 'Offer it when the user wants to see or manage what you shared for them.' The condition is concrete and actionable. There are no explicit when-not conditions or named alternatives, but none of the sibling tools represent a competing account-linking path.

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