Skip to main content
Glama
Sign In
Studio Bridge

Studio Bridge

Official
by Spicy-API
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Connect Studio

studio_connect
DestructiveIdempotent

Generate a short-lived, single-use pairing code for Studio; set reset to true to replace a disconnected or refreshed browser and clear shared requests.

Instructions

Get a short-lived, single-use pairing code to paste into Studio, and show it to the user. If a browser is already paired, the new code replaces that browser only once it is entered. Set reset to true when the user asks for a new code or says the Studio page was refreshed or lost its connection; this disconnects the current browser immediately and clears its shared requests.

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

Input Schema

NameRequiredDescriptionDefault
resetNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • changedOutput schema / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "baseUrl": {
-        "type": "string"
-      },
-      "code": {
-        "type": "string"
-      },
-      "expiresAt": {
-        "type": "number"
-      },
-      "paired": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "baseUrl",
-      "paired"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "error": {
-        "additionalProperties": false,
-        "properties": {
-          "code": {
-            "type": "string"
-          },
-          "message": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "code",
-          "message"
-        ],
-        "type": "object"
-      }
-    },
-    "required": [
-      "error"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "baseUrl": {
+        "type": "string"
+      },
+      "code": {
+        "type": "string"
+      },
+      "expiresAt": {
+        "type": "number"
+      },
+      "paired": {
+        "type": "boolean"
+      },
+      "replacesExisting": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "baseUrl",
+      "paired"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "error": {
+        "additionalProperties": false,
+        "properties": {
+          "code": {
+            "type": "string"
+          },
+          "message": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "code",
+          "message"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]
  2. First observedv0.2.1

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false, idempotentHint=true), the description discloses traits annotations cannot express: the code is short-lived and single-use, a new code only replaces the existing browser once entered, and reset disconnects the current browser immediately and clears its shared requests. This is exactly the 'what gets destroyed' detail an agent needs before calling a destructive tool.

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 core action and the instruction to surface the code to the user are front-loaded in the first sentence, followed by replacement semantics and then the reset guidance. Every sentence carries distinct, non-redundant information.

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?

An output schema exists, so return-value shape need not be described, and the description instead covers the operational gaps: lifecycle of the code, replacement behavior, and the destructive branch via reset. For a one-parameter tool with rich annotations, this is complete.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden for the single parameter, and it does: it names the reset flag and specifies precisely when to set it and what the side effect is (immediate disconnect plus clearing shared requests). No meaning is left to inference.

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+resource (get a short-lived, single-use pairing code for Studio) and even includes the required follow-through action (show it to the user). The sibling tools all handle Studio requests, so this connection/bootstrapping role is clearly distinct from them.

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 an explicit trigger for the reset parameter (user asks for a new code, or the Studio page refreshed / lost its connection), which is strong conditional guidance. It does not, however, state when to reach for this tool versus the sibling request-handling tools, leaving that routing implicit.

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

Deploy Server

Other Tools