Skip to main content
Glama
Sign In

Connections

by icu.connections
OverviewDiscussionsAdmin

Ask the member to copy a connection: mint a one-tap Studio link

connections_copy_connection_link
Destructive

Mint a one-tap link that hands a copy (or move) of one connected service from one of the member's workspaces into another to the member, for when the member wants to confirm it themselves. You do not need this to copy: connections_copy_connection copies or moves the connection directly whenever the member's reach covers both workspaces (their own, or ones shared to them in full), so call that first. Use this link when the member asks to confirm it, or when connections_copy_connection returns cross_workspace_refused with a share-scope reason. Send the member the returned url: it opens in Studio signed in as them, says what moves where, and copies only when they tap Confirm. It works once, only for their account, for 10 minutes. Nothing is copied by this call, and you cannot confirm it yourself. Both workspaces must be the member's own; for a workspace shared to them, use connections_copy_connection. Returns {url, expiresAt}.

Input Schema

NameRequiredDescriptionDefault
modeNocopy (default) shares the credential; move relocates the connection.
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
projectNoWorkspace to run this call in (id or name).
toProjectYesThe receiving workspace's project id, ref or company id.
connectionIdYesThe SOURCE connection's id (a UUID from /v1/connected-services).
instanceNameNoOptional: the connection's name in the receiving workspace (defaults to its current name).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / person
      Added value: +{
+  "description": "Linked person to run this call as (first name). Omit to run as the connection's holder.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Workspace to run this call in (id or name).",
+  "type": "string"
+}
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true annotation: the link is single-use, bound to the member's account, expires in 10 minutes, opens signed in as them, and confirms only on their tap. It also discloses that this call itself copies nothing and that the agent cannot confirm it, which frames where the destructive potential actually lives.

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?

Front-loaded with the artifact and the routing decision, then behavior, then return value. Dense but every clause carries information; the only waste is restating connections_copy_connection's role twice.

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 supplies the return shape ({url, expiresAt}) and what to do with it (send the url to the member). For a non-idempotent, expiring, human-in-the-loop artifact, all decision-relevant facts are present.

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 already 100%, so the baseline is 3. The description still adds meaning by constraining toProject/workspace semantics ('both workspaces must be the member's own') and reinforcing that mode is copy-or-move, which the schema states more tersely.

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 and artifact: mint a one-tap link that hands a copy (or move) of a connection between workspaces to the member. It explicitly distinguishes the artifact from the action, and names the sibling (connections_copy_connection) that performs the copy directly.

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?

Gives an explicit default ('call that first'), two named trigger conditions (member asks to confirm; connections_copy_connection returns cross_workspace_refused with a share-scope reason), and an exclusion (for a workspace shared to them, use connections_copy_connection). Nothing about routing 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 Connections 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