Skip to main content
Glama
CodesWhat

portkey-admin-mcp

by CodesWhat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_workspace

Create a new workspace to isolate resources, API keys, and team members, with optional configuration for rate limits, usage limits, metadata, and default assignment.

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.

Input Schema

TableJSON 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

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool call succeeded and returned structured data
dataNoStructured success payload when ok is true
errorNoStructured error payload when ok is false

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. Addedv1.0.1
  3. Removed
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With annotations already indicating a non-read-only, non-idempotent mutation, the description adds useful behavioral details: slug auto-generation when omitted and the returned fields (id, name, slug). This is meaningful context beyond the structured annotation data, though it does not detail every side effect.

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 tight sentences front-load the action and purpose, then add the key default behavior and return value. Every sentence earns its place; no filler or redundant expansion.

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?

The tool is complex (8 parameters, nested rate/usage-limit objects), but the schema and output schema cover those details thoroughly. The description supplies the important high-level context, isolation purpose, and creation behavior, making it adequate without needing to enumerate nested settings.

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?

The input schema has 100% property description coverage, so the baseline is 3. The description repeats the slug auto-generation rule already present in the schema and does not add meaning for the other seven parameters.

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 states a specific action and resource: 'Create a workspace to isolate resources, API keys, and team members.' This clearly differentiates the tool from the many sibling create_* tools that create API keys, providers, virtual keys, prompts, or other entities.

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?

It provides clear usage context by explaining the purpose ('to isolate resources, API keys, and team members'), which implies when workspace creation is appropriate. It does not explicitly name alternatives or exclusions, so it stops 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.

Deploy Server

Other Tools