Tokenrip

Show folder

folder_show

Read-onlyIdempotent

Get a folder's details: folder is its id (any kind: personal, team or workspace), or its slug: in workspaceId when given, else in team, else one of your personal folders. artifact_count is its live files (null for a workspace folder).

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

Input Schema

Name	Required	Description
`team`	No	With a folder slug: the team (slug or id) it belongs to.
`folder`	Yes	The folder: its id (any kind), or its slug: in workspaceId when given, else in team, else one of your personal folders.
`workspaceId`	No	With a folder slug: the workspace it is in (its id or its slug).

Output Schema

Name	Required	Description	Default
`folder`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 12, 2026
- removedOutput schema / properties / folder / properties / audience
```
Removed value: -{
-  "enum": [
-    "internal",
-    "shared"
-  ],
-  "type": "string"
-}
```

Changed2 schema fields changedOct 27, 2026

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"
+]

Changed5 schema fields changedOct 24, 2026

changedInput schema / properties / workspaceId / description

Previous value: -"With a folder slug: the workspace it is in."New value: +"With a folder slug: the workspace it is in (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.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile needs no restating, and none is repeated. The description adds one genuine behavioral detail beyond them: artifact_count reflects live files and is null for a workspace folder. It says nothing about permissions or error behavior when a slug resolves to nothing.

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?

A single sentence, front-loaded with purpose and with zero padding or redundancy. The nested colon chains pack the resolution precedence efficiently, though they make it slightly dense to parse on first read.

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 annotations, an output schema, and full schema description coverage, the description only needs to explain purpose and lookup precedence, and it does both. The main residual gap is that it never mentions the failure case when a folder id or slug does not resolve.

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 100%, so the schema already documents all three parameters with the same resolution rule the description repeats for folder. The added meaning is marginal beyond the schema, and team and workspaceId receive no description treatment at all, which the high coverage baseline permits.

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 ("Get a folder's details") and narrows scope to a single folder, which contrasts implicitly with folder_list. It does not name any sibling or spell out the read-one-vs-list distinction, so it falls short of a 5.

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?

Use is only implied: an agent can infer this is the single-folder lookup versus folder_list or team_show, but no when-to-use condition or explicit alternative is given. The resolution precedence (workspaceId, else team, else personal) is useful context, but it is lookup mechanics rather than guidance on choosing this tool.

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.