Skip to main content
Glama

workspace_update

Edit the active workspace (or one named by workspace_id): its name, description, logo_url, and/or settings. Requires ADMIN role in that workspace. settings is MERGED, not replaced — send only the keys you want to change (e.g. {"translation_glossary": "..."} or {"translation_tts_provider": "cartesia"}); other keys are left intact. Omit workspace_id to target the workspace this MCP key is currently routed to (see workspace.current).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "workspace_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew workspace name. Omit to leave unchanged.
logo_urlNoNew workspace logo URL. Omit to leave unchanged.
settingsNoPartial settings object, MERGED into the existing workspace.settings JSONB (PATCH semantics). Only the keys you send change. Common keys: translation_glossary, translation_mt_provider, translation_tts_provider, translation_tts_voice, translation_languages, translation_default_lang, meeting_bot_name (the name a meeting bot with no agent joins Meet / Teams / Zoom under, e.g. "<owner>'s notetaker"; a host admits a lobby guest by this name).
descriptionNoNew workspace description. Omit to leave unchanged.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
workspace_idNoNumeric workspace id to update. Omit to target the currently-routed workspace (workspace.current).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / settings / description
      Previous value: -"Partial settings object, MERGED into the existing workspace.settings JSONB (PATCH semantics). Only the keys you send change. Common keys: translation_glossary, translation_mt_provider, translation_tts_provider, translation_tts_voice, translation_languages, translation_default_lang."New value: +"Partial settings object, MERGED into the existing workspace.settings JSONB (PATCH semantics). Only the keys you send change. Common keys: translation_glossary, translation_mt_provider, translation_tts_provider, translation_tts_voice, translation_languages, translation_default_lang, meeting_bot_name (the name a meeting bot with no agent joins Meet / Teams / Zoom under, e.g. \"<owner>'s notetaker\"; a host admits a lobby guest by this name)."
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  3. Added
  4. Removed
  5. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive mutation; the description goes beyond that by disclosing the merge/PATCH semantics of settings ('MERGED, not replaced... other keys are left intact') and the ADMIN authorization prerequisite. It does not describe the response payload or what happens on partial failure, so with no output schema there is still a small gap. Minor note: idempotentHint=false sits slightly awkwardly against PATCH-merge behavior, but the description makes no idempotency claim, so this is not a contradiction.

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?

Three tight sentences, front-loaded with the action and scope, then authorization, then the one non-obvious semantic (merge behavior), then default-targeting. Every clause carries information; nothing is restated from the title.

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?

For a 6-parameter, nested-object mutation with a 0-required schema and an ADMIN gate, the definition covers scope, authorization, targeting defaults, and the risky merge semantic. Missing only return-value expectations, which the absence of an output schema leaves 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%, so the baseline is 3, but the description adds real meaning: it explains the omission-default for workspace_id and spells out merge semantics for settings with concrete example keys. The in_workspace parameter is left entirely to the schema, which is a small missed opportunity given that it changes which workspace the call applies to.

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 (Edit), a specific resource (the active workspace or one named by workspace_id), and enumerates the editable fields (name, description, logo_url, settings). The sibling tools workspace_create and workspace_member_update cover clearly different operations, so the agent can distinguish this without opening a schema.

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?

Gives concrete activation context: 'Requires ADMIN role in that workspace' and 'Omit workspace_id to target the workspace this MCP key is currently routed to (see workspace.current)'. It names the workspace.current sibling as the way to discover the default target. No explicit when-not-to-use or alternative named, which keeps it just 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.