Tokenrip

List workspaces

workspace_list

Read-onlyIdempotent

List accessible workspaces with your live role (admin, editor or viewer), guest (true where you were added rather than owning it or being in its team) and operation capabilities. needsYou counts what waits on you (this key) in each workspace, as cards: approved tasks for this key to carry out, reviews addressed to this key (the In review children of one parent count once) and To do tasks naming this key. workspace_load lists them under waiting; decide reviews with task_decide. unreadMessages counts the workspace chat's messages this key has not been shown, never its own (at most 100; unreadMessagesTruncated when there are more): workspace_load carries the newest, and message_read reads the chat.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "workspace_list"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No

Output Schema

Name	Required	Description	Default
`items`	Yes
`nextCursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 12, 2026
- addedOutput schema / properties / items / items / properties / unreadMessages
```
Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
```
- addedOutput schema / properties / items / items / properties / unreadMessagesTruncated
```
Added value: +{
+  "type": "boolean"
+}
```
- changedOutput schema / properties / items / items / required
```
Previous value: -[
-  "needsYou"
-]New value: +[
+  "needsYou",
+  "unreadMessages",
+  "unreadMessagesTruncated"
+]
```
First observedOct 23, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is low; the description goes further by explaining counting rules (In-review children count once), that unreadMessages excludes the key's own messages, the cap of 100 and the unreadMessagesTruncated signal. It omits pagination behavior for limit/cursor, which is the one behavioral gap.

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?

The description is front-loaded with the correct information, but a large share of it explains return-value semantics (needsYou breakdown, unreadMessages) that the existing output schema already documents. Long run-on sentences with parenthetical asides make it dense to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Return-shape explanation is largely redundant given the output schema, while the genuinely undocumented area — limit/cursor pagination — receives no treatment. For a simple two-parameter list tool this is workable but incomplete on the one axis the schema leaves blank.

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

Parameters2/5

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

Neither parameter is mentioned anywhere in the description, and schema description coverage is 0%, so the meaning of 'limit' (default 50, max 100) and especially 'cursor' (numeric pattern, opaque resume token) must be inferred. With no compensation in the text, an agent has no guidance on how to page through results.

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 opening sentence states a specific verb and resource ('List accessible workspaces') and immediately enumerates the returned facets (role, guest, operation capabilities), so an agent knows exactly what this call yields. It also implicitly separates itself from workspace_load, which is named as the place where the waiting items are surfaced.

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?

The description routes the agent onward: decide reviews with task_decide, read chat with message_read, and get the actual waiting items via workspace_load. It never says when NOT to use this tool (e.g. versus workspace_show or workspace_view_context for a single workspace), so there is clear context but no explicit exclusions.

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.