Skip to main content
Glama

Switch workspace

switch_workspace

Bind this connection to another workspace (team) the user belongs to. Later calls spend that workspace's credits.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "switch_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare non-readonly, non-destructive, closed-world; the description adds real context they do not carry: the change is connection-scoped and persists into later calls, and it redirects credit consumption. It also implies a membership precondition ('the user belongs to'). Not disclosed: behavior if the user is not a member, or whether the binding survives across sessions.

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?

Two short sentences, zero filler, and the primary effect is front-loaded before the downstream consequence. Nothing needs trimming and nothing is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple — one parameter, a connection-level state change — and an output schema exists to cover return values. The definition covers what changes and why, which is sufficient; only error/precondition details are absent, and those are minor for this complexity.

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?

Schema coverage is 0% with one required parameter, so the description must carry the meaning. It does clarify that workspace_id must reference a workspace the user belongs to, but says nothing about identifier format (ID vs. name) or how to obtain a valid value, leaving a gap the schema does not fill.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and effect: 'Bind this connection to another workspace (team)'. The scope is precise and the parenthetical disambiguates workspace as team/billing context, which no sibling tool covers. It stops short of explicitly contrasting with siblings, but the action is unmistakable.

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?

The second sentence gives the operative reason to call it — subsequent calls draw on that workspace's credits — which tells an agent when this is appropriate. There is no explicit when-not or named alternative, so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources