Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

workspace_create

Create a new team workspace owned by the calling user. Returns its id and slug — pass either to workspace.switch to start working inside it. slug is derived from name when omitted. NOT idempotent: calling twice with the same name yields two workspaces (the second gets a -1 slug suffix), so check workspace.list first if the workspace may already exist. A user may own at most 25 team workspaces.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesWorkspace display name, e.g. 'TUI BLUE'.
slugNoURL-friendly slug: lowercase letters, digits and single dashes between them (e.g. 'tui-blue'), max 100 chars. Omit to derive one from `name` (lowercased, spaces to dashes, uniqueness suffix added when taken). An explicit slug is NOT auto-uniquified — a collision is an error.
descriptionNoOptional workspace description.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

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

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare idempotentHint=false, but the description goes well beyond them: it explains *why* (a second call yields a duplicate workspace with a `-1` slug suffix), states a hard quota (max 25 owned team workspaces), and describes return values in the absence of an output schema. This is exactly the added context the annotations cannot carry.

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 action and return values, then the operational caveats (non-idempotency, quota). Every sentence carries distinct, decision-relevant information with no filler.

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 creation tool with no output schema and no annotations on side effects, the description covers the return payload, the non-idempotent duplicate behavior, the slug derivation rule, and the ownership quota — everything an agent needs to call it safely.

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 description coverage is 100%, so the schema already documents all four parameters including slug derivation and the collision-error behavior. The description's 'slug is derived from name when omitted' largely restates the schema rather than adding new syntax or format meaning, so the baseline 3 applies.

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+resource ('Create a new team workspace') with scope ('owned by the calling user') and an immediate statement of what it returns. It is clearly separable from siblings like workspace_list, workspace_switch, and workspace_update.

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?

Explicitly routes the agent: check `workspace.list` first if the workspace may already exist, and pass the returned id/slug to `workspace.switch` to work inside it. Both the when-to-use and the alternative-tool path are stated, not implied.

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