Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

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).

Input Schema

TableJSON 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.
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
    • 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"
+}
  2. Added
  3. Removed
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare write/non-destructive/idempotent=false; the description adds two high-value traits: an ADMIN role requirement and, crucially, that `settings` is MERGED (PATCH) rather than replaced, with concrete examples. These are exactly the behavioral facts an agent needs before mutating a workspace.

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?

Front-loaded with the core action and target, then layers auth, merge semantics, and default targeting in descending priority. Dense but every clause carries actionable information; no filler.

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?

Covers the essentials for a 6-param mutation with no output schema: target resolution, permissions, and merge behavior. Minor gaps remain (in_workspace override behavior and expected response), but with annotations carrying the safety profile these are not blocking.

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 meaning: it explains the workspace_id omission default and illustrates the merge/patch semantics of the nested settings object with example payloads. It leaves in_workspace unexplained, so it is not a full 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?

Specific verb ("Edit") plus resource ("workspace") and an explicit enumeration of the editable fields (name, description, logo_url, settings). An agent can distinguish this from workspace_create (new) and workspace_current (read) 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly states the context (edit the active workspace or one addressed by workspace_id) and the default targeting behavior when workspace_id is omitted, referencing workspace.current. It does not explicitly name when-not or route to siblings like workspace_member_update, so it stops short of full alternative guidance.

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

All dialogbrain 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