Skip to main content
Glama

create_workspace

Create a workspace to isolate resources, API keys, and team members. Returns the new workspace ID, name, and slug, with optional auto-generated slug.

Instructions

Create a workspace to isolate resources, API keys, and team members. If slug is omitted it is auto-generated from the name; returns the new workspace id, name, and slug.

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": {
      "name": "<name>"
    },
    "name": "create_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the workspace
slugNoURL-friendly slug (auto-generated if not provided)
usersNoExisting user IDs to add
metadataNoCustom metadata key-value pairs
is_defaultNoSet as default workspace (1 = yes, 0 = no)
descriptionNoDescription of the workspace
rate_limitsNoInitial workspace rate-limit settings
usage_limitsNoInitial workspace usage-limit settings

Output Schema

NameRequiredDescriptionDefault
okYesCall succeeded
dataNoSuccess payload
errorNoFailure details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.16.5
    • changedOutput schema / properties / data / description
      Previous value: -"Structured success payload when ok is true"New value: +"Success payload"
    • changedOutput schema / properties / error / description
      Previous value: -"Structured error payload when ok is false"New value: +"Failure details"
    • changedOutput schema / properties / error / properties / details / description
      Previous value: -"Optional structured error details"New value: +"Extra error details"
    • changedOutput schema / properties / error / properties / message / description
      Previous value: -"Human-readable error message"New value: +"Error message"
    • changedOutput schema / properties / ok / description
      Previous value: -"Whether the tool call succeeded and returned structured data"New value: +"Call succeeded"
  2. Changed2 schema fields changedv1.0.9
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changedv0.12.2
    • changedInput schema / properties / usage_limits / items / properties / next_usage_reset_at / anyOf
      Previous value: -[
      -  {
      -    "format": "date-time",
      -    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "format": "date-time",
      +    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  4. Changed3 schema fields changedv0.11.5
    • addedInput schema / properties / rate_limits
      Added value: +{
      +  "description": "Initial workspace rate-limit settings",
      +  "items": {
      +    "properties": {
      +      "type": {
      +        "description": "Whether the limit counts requests or tokens",
      +        "enum": [
      +          "requests",
      +          "tokens"
      +        ],
      +        "type": "string"
      +      },
      +      "unit": {
      +        "description": "Rate window: requests per day, hour, or minute",
      +        "enum": [
      +          "rpd",
      +          "rph",
      +          "rpm"
      +        ],
      +        "type": "string"
      +      },
      +      "value": {
      +        "description": "Maximum count in the selected rate window",
      +        "maximum": 9007199254740991,
      +        "minimum": 0,
      +        "type": "integer"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / usage_limits
      Added value: +{
      +  "description": "Initial workspace usage-limit settings",
      +  "items": {
      +    "properties": {
      +      "alert_threshold": {
      +        "description": "Percentage of the limit that triggers an alert",
      +        "exclusiveMinimum": 0,
      +        "type": "number"
      +      },
      +      "credit_limit": {
      +        "description": "Maximum cost or token usage for the workspace",
      +        "exclusiveMinimum": 0,
      +        "type": "number"
      +      },
      +      "next_usage_reset_at": {
      +        "anyOf": [
      +          {
      +            "format": "date-time",
      +            "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "description": "Next reset timestamp in ISO 8601 format"
      +      },
      +      "periodic_reset": {
      +        "anyOf": [
      +          {
      +            "enum": [
      +              "monthly",
      +              "weekly"
      +            ],
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "description": "Built-in weekly or monthly reset cadence"
      +      },
      +      "periodic_reset_days": {
      +        "anyOf": [
      +          {
      +            "maximum": 365,
      +            "minimum": 1,
      +            "type": "integer"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "description": "Custom reset cadence in days, from 1 through 365"
      +      },
      +      "type": {
      +        "description": "Whether the limit measures cost or tokens",
      +        "enum": [
      +          "cost",
      +          "tokens"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / users
      Added value: +{
      +  "description": "Existing user IDs to add",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  5. Addedv1.0.1
  6. Removed
  7. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the slug auto-generation fallback and the returned fields, but the slug fallback is also stated in the schema and the return fields are covered by the existing output schema, so genuine value beyond structured data is thin. Nothing is said about permission requirements or what happens if name/slug collide.

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?

Two sentences, both front-loaded: purpose first, then the one non-obvious creation behavior and the return shape. No filler, no restating of the tool name as a sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Return values are covered by the output schema and all parameters by the schema, so the description only needs to frame intent and defaults, which it partly does. However, for a create tool with rich nested options (users, is_default, rate_limits, usage_limits) and no idempotency guarantee, it leaves the agent without guidance on defaults or duplicate-name behavior.

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 8 parameters including the nested rate_limits and usage_limits objects. The description only touches slug behavior, which the schema also covers, so it adds no meaning beyond the input schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ("Create a workspace") and adds a scope rationale ("to isolate resources, API keys, and team members"), which distinguishes it from siblings like update_workspace, delete_workspace, and create_scim_workspace_mapping. It stops short of explicitly naming a sibling to route against, but the creation semantics are unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by "Create" and the isolation rationale tells the agent why a workspace might be warranted, but there is no explicit when-to-use/when-not guidance, no prerequisites, and no pointer to update_workspace for modifying an existing workspace or to add_workspace_member for membership.

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

Deploy Server

Other Tools