Skip to main content
Glama

select_workspace

Switch which workspace (client) you are working in. Drafts, schedules, channels and analytics from then on are that workspace's, and the choice sticks for later calls and later messages until it is changed again. Use ONLY when the user asks to change client or workspace, like "switch to Acme", "work on Acme now". Do NOT use it to write something FOR a client while staying where you are; that is draft_post with the topic. This changes the standing client. To ask one thing about another client ("how did Acme's posts do?"), pass workspace to that tool instead: every workspace tool takes it, for that call only, and the current workspace stays as it is.

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

Input Schema

NameRequiredDescriptionDefault
workspaceYesWorkspace name (e.g. 'Acme') or numeric id, as returned by list_workspaces

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, which tells the agent nothing about scope. The description adds the crucial behavior that the change is sticky ("sticks for later calls and later messages until it is changed again") and enumerates what is affected (drafts, schedules, channels, analytics), which is exactly the stateful side effect an agent needs before invoking it.

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?

The critical points are front-loaded: what it does, how long it lasts, when to use, when not to use, and the alternative. It is longer than most descriptions but nearly every sentence carries a distinct constraint; the "This changes the standing client" sentence partially restates the opening and could be trimmed.

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 one required parameter, full schema coverage and no output schema, the definition covers everything an agent needs: the semantics of the state change, its persistence, the invocation conditions, and the sibling-based alternative. Nothing material is left to inference.

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% and the schema already documents `workspace` as a name or numeric id from list_workspaces, so the baseline is 3. The description adds real meaning beyond that by explaining that every workspace tool also accepts this parameter on a per-call basis, clarifying the difference between the standing client and a one-off target.

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 opens with a specific verb and resource ("Switch which workspace (client) you are working in") and immediately states the scope of effect: drafts, schedules, channels and analytics belong to that workspace afterward. It also distinguishes itself from draft_post and from the per-call `workspace` parameter, so an agent can tell exactly what this tool does versus siblings.

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?

Explicit when-to-use ("Use ONLY when the user asks to change client or workspace") with quoted example utterances, plus explicit when-not ("Do NOT use it to write something FOR a client while staying where you are; that is draft_post") and a named alternative for the read-one-client case. All three routing branches are covered with concrete examples.

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