Tokenrip

Create workspace

workspace_create

Create a personal workspace, or a team one (team: the team's slug or id; team owners and admins). name defaults to the slug. Everyone in a workspace sees all of it: keep private work in a separate workspace. A team-owned workspace needs the team to be on a paid plan. An owner without room for another (a team without a paid plan, or an owner at its maximum) is refused WORKSPACE_LIMIT_REACHED, whose details name the owner, plan, limit and count. Tell the person; at the maximum, deleting a workspace makes room. Do not retry.

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

Input Schema

Name	Required	Description
`why`	No	Required for workspace items: one sentence on what the person is trying to accomplish, in their terms, not a description of this edit. Every workspace write takes one; sessions and summaries record themselves from it. At most 300 characters.
`name`	No	Display name; defaults to the slug.
`slug`	Yes	The workspace slug: unique within its owner (you, or the team).
`team`	No	Make it a team workspace: the team's slug or id (team owners and admins; the team needs a paid plan).
`description`	No

Output Schema

Name	Required	Description	Default
`workspace`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

changedInput schema / properties / team / description

Previous value: -"Make it a team workspace: the team's slug or id (team owners and admins; the team needs Pro or Power)."New value: +"Make it a team workspace: the team's slug or id (team owners and admins; the team needs a paid plan)."

Changed1 schema field changedOct 27, 2026

changedInput schema / properties / team / description

Previous value: -"Make it a team workspace: the team's slug or id (team owners and admins; the Team plan)."New value: +"Make it a team workspace: the team's slug or id (team owners and admins; the team needs Pro or Power)."

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare non-readonly, non-idempotent, non-destructive. The description adds substantial context beyond that: the visibility model ('Everyone in a workspace sees all of it'), the paid-plan prerequisite, the exact error code WORKSPACE_LIMIT_REACHED with its detail fields, an explicit 'Do not retry' instruction, and the remedy at the limit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and variant, then prerequisites, then the failure mode. Dense but every sentence carries information; only the clipped fragments ('Tell the person; at the maximum, deleting a workspace makes room') reduce readability slightly.

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 create tool with an output schema already documenting returns, the description covers the remaining needs: plan prerequisites, permission scope, visibility implications, and precise failure handling. Nothing an agent needs to call it correctly is missing.

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 coverage is 80%, so parameters are already well documented. The description restates what the schema says (name defaults to slug, team needs owners/admins and a paid plan) rather than adding new syntax or format meaning; its value lies mainly in behavioral constraints rather than parameter interpretation.

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 and resource ('Create a personal workspace, or a team one') and immediately distinguishes the two variants via the team parameter. An agent can tell this apart from workspace_update or team_create 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 situational guidance — use a separate workspace for private work because everyone sees all of a workspace, and team workspaces require owners/admins and a paid plan. It does not explicitly route to siblings such as workspace_adopt or workspace_member_add, but the conditions for calling this tool are clear.

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

All Tokenrip tools Inspect

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.