Tokenrip

Move artifacts or a folder into workspace

workspace_adopt

DestructiveIdempotent

Move eligible standalone artifacts of yours (artifactIds, optionally into destinationFolderId) or a personal folder with its files (folder: its id or slug) into a workspace. Everyone in the workspace then sees them, with every version they keep. The move is atomic and does not copy content.

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

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.
`folder`	No	A personal folder to move in with its files: its id, or its slug. Not with artifactIds.
`artifactIds`	No	Standalone artifacts of yours to move in (id, alias in any form, or page URL; at most 500, each once). Not with folder.
`workspaceId`	Yes	The workspace: its id or its slug.
`destinationFolderId`	No	With artifactIds: the workspace folder to file them in (its id); null or omitted files them at the root.

Output Schema

Name	Required	Description	Default
`folderId`	Yes
`artifactIds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 12, 2026

removedInput schema / properties / audience

Removed value: -{
-  "description": "internal (the default for internal members) or shared (the only choice for external editors).",
-  "enum": [
-    "internal",
-    "shared"
-  ],
-  "type": "string"
-}

Changed5 schema fields changedOct 24, 2026

changedInput schema / properties / workspaceId / description

Previous value: -"The workspace id (UUID)."New value: +"The workspace: its id or its slug."

removedInput schema / properties / workspaceId / format
```
Removed value: -"uuid"
```
addedInput schema / properties / workspaceId / maxLength
```
Added value: +64
```
addedInput schema / properties / workspaceId / minLength
```
Added value: +1
```

removedInput schema / properties / workspaceId / pattern

Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

First observedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description adds real consequences: visibility becomes workspace-wide with 'every version they keep', the operation is atomic, and no content is copied. What it omits is whether the move can be reversed or what an agent loses by relocating an artifact out of personal scope, which matters for a destructive-classified operation.

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, no filler, with the resource and the artifact-vs-folder branch front-loaded and the behavioral consequences (visibility, versions, atomicity, no copy) packed into the second. Every clause carries information an agent needs.

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?

With an output schema, full parameter coverage, and rich annotations, the remaining description burden is behavioral, and the description covers visibility and version effects well. It falls short only on the eligibility criteria and reversibility of a move the annotations mark as destructive.

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 baseline is 3 and the schema already documents why, folder, artifactIds, workspaceId, and destinationFolderId in more detail than the description does. The description only reframes those parameters as two exclusive modes and notes destinationFolderId is optional, adding framing but no new syntactic meaning.

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 names a specific verb (move) and two precisely scoped resources: 'eligible standalone artifacts of yours' and 'a personal folder with its files', plus the destination (a workspace). The internal mode split, keyed to artifactIds vs folder, lets an agent distinguish this from a generic artifact move before opening the schema.

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?

The description conveys the context of consolidation into a shared workspace and states the two mutually exclusive input modes, which is implied usage guidance. However, it never says when to prefer this over a sibling such as artifact_move, and 'eligible' is left undefined, so the agent cannot tell what disqualifies an artifact from adoption.

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.