Tokenrip

Update workspace

workspace_update

DestructiveIdempotent

Update workspace name, description (null clears) or history (how many earlier versions whole-file updates keep: off, all or a count; null clears it, reading as off), any of them. Workspace administrators only.

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_update"
  }
}

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
`history`	No	How many earlier versions whole-file updates in this workspace keep: off, all, or a number from 1 to 100; null clears it (reads as off). A folder's or file's own setting wins. Takes effect at each file's next write; deletes nothing now.
`description`	No
`workspaceId`	Yes	The workspace: its id or its slug.

Output Schema

Name	Required	Description	Default
`workspace`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

addedInput schema / properties / history

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "enum": [
+            "off",
+            "all"
+          ],
+          "type": "string"
+        },
+        {
+          "maximum": 100,
+          "minimum": 1,
+          "type": "integer"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "How many earlier versions whole-file updates in this workspace keep: off, all, or a number from 1 to 100; null clears it (reads as off). A folder's or file's own setting wins. Takes effect at each file's next write; deletes nothing now."
+}

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

A3.6/5.0

Behavior4/5

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

Adds two behaviors beyond the annotations: the admin-only authorization requirement, and the fact that history takes effect at each file's next write and 'deletes nothing now'. Annotations already flag destructiveHint/idempotentHint, so the description's contribution is meaningful supplementary context rather than the full burden.

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

Conciseness3/5

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

A single dense sentence with deeply nested parentheticals that are hard to parse on first read. The scope is front-loaded, but the parenthetical clauses obscure rather than clarify.

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?

An output schema exists and the annotations cover the safety profile, so the description needs only to explain mutations and constraints. It does so for most fields, with the only gap being the unchanged 'why' parameter and return-value expectations.

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?

With 60% schema description coverage, the description clarifies the tricky parts (null clears description; history accepts off/all/count and null reads as off). It does not mention the 'why' parameter at all, leaving the schema to explain it.

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?

States a specific verb and resource plus enumerated fields (name, description, history), so it is clearly distinct from workspace_create/workspace_delete. It does not explicitly contrast with sibling tools like folder_update, but the resource is 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?

'Workspace administrators only' gives a real precondition and 'any of them' implies partial updates are allowed. However, there is no statement of when to prefer this over workspace_create or other workspace siblings, so usage must be inferred.

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.