Skip to main content
Glama

Connections

by icu.connections
OverviewDiscussionsAdmin

Switch which workspace this connection uses

connections_switch_workspace
Idempotent

Use this the moment the member says they are in the wrong workspace - 'wrong workspace', 'wrong company', 'switch me to ', or when they confirm a switch you offered because data they expected is missing. CALL IT STRAIGHT AWAY WITH NO workspace when they did not name one: if only one other workspace is reachable there is nothing to choose, so it just moves and tells you where it landed - do NOT call connections_list_companies first, and do not ask a question the member has already answered. If several are reachable the reply carries the choices; read those names out, let them pick, and call again with workspace. Moves THIS connection only, effective on the next call, and copies or deletes nothing. Pass remember:true when they want every FUTURE assistant they connect to start there too. Say the reply's workspace name back to them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rememberNoAlso make this the workspace that any NEW assistant connection starts in. Default false - ask the member before setting it.
workspaceNocompanyId (preferred) or the exact workspace name. OMIT when the member did not name one - with a single alternative the tool resolves it, with several it hands back the choices to put to them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[]
  2. Changed2 schema fields changed
    • changedInput schema / properties / workspace / description
      Previous value: -"companyId (preferred) or the exact workspace name, from connections_list_companies."New value: +"companyId (preferred) or the exact workspace name. OMIT when the member did not name one - with a single alternative the tool resolves it, with several it hands back the choices to put to them."
    • removedInput schema / required
      Removed value: -[
-  "workspace"
-]
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover safety (readOnly=false, idempotent=true, destructive=false), and the description goes well beyond them: it discloses that only THIS connection moves, that the change is effective on the next call, that nothing is copied or deleted, and that remember:true affects future assistant connections. These are real behavioral traits an agent must know.

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-loads the trigger condition and stays on task, but the dense run-on sentences and shouted emphasis ('STRAIGHT AWAY', 'do NOT') make it longer than necessary. Every clause is informative, but it could be tightened without losing meaning.

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?

No output schema exists, so the description carries the return-value burden, and it does: it explains that a single alternative resolves silently and reports where it landed, while multiple alternatives return choices. Combined with trigger and remember semantics, an agent has everything needed to call and interpret it.

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 operational meaning the schema lacks: OMIT `workspace` when unnamed, with single vs. multiple alternatives producing different returns. It also reinforces the opt-in nature of `remember`. Slight overlap with the schema keeps it from a 5.

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 (switch) and resource (which workspace this connection uses), and explicitly differentiates from the sibling connections_list_companies by telling the agent NOT to call it first. An agent can identify the tool's job and its boundaries without opening any 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?

Gives explicit trigger phrases ('wrong workspace', 'switch me to <name>', confirmed switch after missing data), states when to call with no argument versus with `workspace`, and names the alternative it is not (connections_list_companies). The single-vs-multiple workspace decision tree is spelled out.

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