The Bridge

Add Redirect URI

add_redirect_uri

Idempotent

Register ONE OAuth redirect (callback) URI on the Bridge app, preserving every already-registered URI — never replaces the list wholesale. The URL must be absolute http(s), e.g. https://app.example.com/auth/oauth-callback or http://localhost:5173/auth/oauth-callback for local dev. Adding a URL that is already registered succeeds as a no-op (added: false). The first URI registered on an app with no default callback also becomes its default callback. Use this when wiring a new environment or fixing a "redirect_uri mismatch" OAuth error; see get_environment_info for the currently registered list, and remove_redirect_uri to unregister one. Before writing app code that consumes this, call get_integration_guide with topic=auth and the framework the app uses.

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": {
      "url": "<url>"
    },
    "name": "add_redirect_uri"
  }
}

Input Schema

Name	Required	Description	Default
`app`	No	Id of the Bridge app to act on for this call (see list_apps). Omit to use the current app.
`url`	Yes	Absolute http(s) callback URL to register, e.g. http://localhost:5173/auth/oauth-callback.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations (readOnly=false, idempotent=true, destructive=false), it discloses that existing URIs are never replaced wholesale, that duplicates succeed as a no-op returning added: false, and that the first URI on an app with no default callback becomes the default — a side effect not visible in annotations.

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 key non-destructive guarantee is front-loaded and each sentence carries information, though the trailing get_integration_guide instruction slightly lengthens an otherwise dense block.

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?

With no output schema, the description compensates by describing return semantics (added: false) and the default-callback side effect, and it covers preconditions (absolute http(s)) and related tools, leaving nothing essential unclear.

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 baseline is 3, but the description adds meaning by stressing that only ONE URI is registered per call and by giving a local-dev example (http://localhost:5173/...) alongside the production example.

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 names a specific verb and resource (register ONE OAuth redirect URI on the Bridge app) and explicitly states the additive scope, distinguishing it from remove_redirect_uri and list_redirect_uris without requiring the schema.

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?

It gives explicit triggers (wiring a new environment, fixing a 'redirect_uri mismatch' error) and routes to named alternatives: get_environment_info for the current list, remove_redirect_uri to unregister, and get_integration_guide for app-side wiring.

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

All The 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.