Skip to main content
Glama
Sign In

Tokenrip

by com.tokenrip
OverviewDiscussionsAdmin

Create folder

folder_create

Create a personal, team (team), or workspace (workspaceId) folder. A workspace folder needs why; team and workspaceId go alone. New folders need no expected revision.

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": "folder_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
whyNoRequired 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.
slugYesThe new folder's slug: 1-64 lowercase letters, digits or hyphens, no leading or trailing hyphen.
teamNoCreate it as this team's folder (slug or id).
workspaceIdNoCreate it in this workspace, by its id or its slug (a workspace folder needs why).

Output Schema

NameRequiredDescriptionDefault
folderYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / audience
      Removed value: -{
-  "description": "A workspace folder's audience: internal (the default for internal members) or shared (the only choice for external editors).",
-  "enum": [
-    "internal",
-    "shared"
-  ],
-  "type": "string"
-}
    • removedOutput schema / properties / folder / properties / audience
      Removed value: -{
-  "enum": [
-    "internal",
-    "shared"
-  ],
-  "type": "string"
-}
  2. Changed2 schema fields changed
    • addedOutput schema / properties / folder / properties / history
      Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "enum": [
+            "off",
+            "all"
+          ],
+          "type": "string"
+        },
+        {
+          "maximum": 100,
+          "minimum": 1,
+          "type": "integer"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedOutput schema / properties / folder / required
      Previous value: -[
-  "id",
-  "slug",
-  "owner_id",
-  "team_id",
-  "artifact_count",
-  "created_at",
-  "updated_at"
-]New value: +[
+  "id",
+  "slug",
+  "owner_id",
+  "team_id",
+  "artifact_count",
+  "history",
+  "created_at",
+  "updated_at"
+]
  3. Changed5 schema fields changed
    • changedInput schema / properties / workspaceId / description
      Previous value: -"Create it in this workspace (a workspace folder needs why)."New value: +"Create it in this workspace, by its id or its slug (a workspace folder needs why)."
    • 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)$"
  4. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare the write/safe/non-idempotent profile, so the bar is lower; the description adds real value by disclosing the optimistic-concurrency expectation ("New folders need no expected revision") and the mutual exclusivity of team/workspaceId. It stops short of stating what happens on slug collision or duplicate creation, which is the main behavioral risk for a non-idempotent write.

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?

Three short sentences, front-loaded with the verb and the mode enumeration, then the constraints. No restatement of schema text and no filler.

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?

Output schema exists and 100% parameter coverage means return values and field formats need no explanation here. The one gap is that the "personal" mode is never tied to an invocation rule (omitting both team and workspaceId); the agent must infer it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description goes beyond per-field docs by describing cross-parameter relationships the schema cannot express: why is conditional on workspaceId, and team/workspaceId are alternatives rather than complements. That is meaningful semantic gain.

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 ... folder") and enumerates the three creation scopes with the parameter that selects each ("team (team)", "workspace (workspaceId)"). An agent can tell immediately which mode it wants without comparing schemas.

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 usage rules: why is required for workspace folders, "team and workspaceId go alone" (mutual exclusion), and no expected revision is needed. It does not point at folder_update or otherwise contrast with siblings, but for a create tool the boundary is largely self-evident.

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

All Tokenrip toolsInspect
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.

Resources