Tokenrip

Empty folder

folder_empty

DestructiveIdempotent

Move the live files in a workspace folder to the trash and leave the folder: folder is its id, or its slug with workspaceId; the workspace is the folder's own. Needs why. expectedWorkspaceRevision is optional: send the folder's workspace revision to refuse (CONFLICT) if it changed since.

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

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`	Yes	The workspace folder: its id, or its slug with workspaceId.
`workspaceId`	No	With a folder slug: the workspace it is in (its id or its slug).
`expectedWorkspaceRevision`	No	Optional, a workspace folder's: refuse (CONFLICT) if the folder changed since this workspace_revision.

Output Schema

Name	Required	Description	Default
`kept`	Yes
`failed`	Yes
`trashed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare destructiveHint and idempotentHint, but the description adds real value beyond them: files move to the trash (implying recoverability) rather than being purged, the folder itself survives, and expectedWorkspaceRevision triggers a CONFLICT on concurrent change. It stops short of stating permissions/auth needs or whether subfolders or non-live (e.g., draft/trashed) files are affected.

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 the action and its key consequence, then the parameter notes; no filler sentences. The telegraphic fragments ('Needs why.', 'the workspace is the folder's own') are dense but slightly harder to parse than plain prose.

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?

Rich supporting structure (full schema descriptions, output schema, annotations) means the description only needs to carry the semantics of the action, which it does. The one meaningful omission for a destructive bulk operation is scope: whether subfolders or already-trashed items are included in the emptying.

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 baseline is 3. The description largely restates the schema (folder id or slug plus workspaceId, the why requirement, the revision conflict) and only adds one genuine nuance: the workspace is the folder's own, i.e. the caller cannot target a different workspace.

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 ('move the live files ... to the trash') and adds the crucial differentiator 'and leave the folder', which separates it from a full folder deletion. An agent can pick this over folder_delete without opening either 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?

Usage is implied by the outcome described (clear out contents but keep the folder), and the 'Needs why' line signals a precondition for workspace writes. However, no alternative is named and there is no explicit when-not guidance (e.g., when to use folder_delete instead, or when emptying is inappropriate).

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.