Skip to main content
Glama

switch_workspace

Read-onlyIdempotent

Redirect all tools to another workspace for the rest of the MCP session by supplying its ID or title from list_workspaces; the previous token stays valid.

Instructions

Point every tool at another workspace (id or title from list_workspaces) for the rest of this MCP session.

Mizito binds a workspace to the token: workspace/switch mints a new token, and the previous one stays valid (verified 2026-11-12), so switching back is free. Kept in memory only: a restart returns to the workspace of the token in .env.

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

Input Schema

NameRequiredDescriptionDefault
workspaceYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the underlying mechanism (workspace/switch mints a new token), that the previous token remains valid so switching back is free, and that state is memory-only and reverts on restart. These are non-obvious operational traits an agent cannot infer from readOnlyHint/idempotentHint=true, and they usefully qualify the safety profile even though token minting is a mild side effect.

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 scope statement and the eligible identifier source are front-loaded in the first sentence, followed by short supporting paragraphs on token and state behavior. No sentence is filler; even the verification date serves as a trust signal for the token claim.

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?

For a one-parameter session-state tool with annotations and an output schema already present, the description covers everything an agent needs: what changes, how long it lasts, how to undo it, and what resets it. Return values are correctly left to the output schema.

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?

With zero schema description coverage, the description carries the parameter burden and does so: it states the single `workspace` value may be either an id or a title, and that both come from list_workspaces. What it does not cover is behavior on an invalid or ambiguous value, so it adds real meaning but is not exhaustive.

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 gives a specific verb and resource ('Point every tool at another workspace'), names the accepted identifier forms, and scopes the effect ('for the rest of this MCP session'). This lets an agent distinguish it from list_workspaces, which is explicitly identified as the id source rather than the switcher.

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 description makes the usage condition clear (obtain an id or title from list_workspaces, then call this to repoint every subsequent tool call for the session) and implies when not to use it by promising that switching back is free. It stops short of explicitly stating preconditions such as validating the workspace exists or warning against use mid-workflow, so it is clear context rather than full when/when-not guidance.

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