Skip to main content
Glama
Sign In

Tokenrip

by com.tokenrip
OverviewDiscussionsAdmin

Show workspace

workspace_show
Read-onlyIdempotent

Read workspace identity, home, and live capabilities. workspaceId is the workspace's id or its slug; a slug that names two workspaces you reach is refused AMBIGUOUS_REFERENCE, listing each by id and home. Use workspace_sessions for who worked here recently. A platform admin may show any workspace (read and remove capabilities), but loading it needs membership.

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

Input Schema

NameRequiredDescriptionDefault
workspaceIdYesThe workspace: its id or its slug.

Output Schema

NameRequiredDescriptionDefault
workspaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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)$"
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only annotations, it discloses an important failure mode when a slug is ambiguous (AMBIGUOUS_REFERENCE) and explains that the error lists matching workspaces by id and home. It also adds authorization nuance for platform admins and the membership requirement for loading.

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?

The description is front-loaded with the core action and remains tight while covering the ambiguity behavior, alternative tool, and admin membership nuance. Every sentence contributes useful information.

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

Completeness5/5

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

With a single fully described parameter, an output schema, and read-only annotations, the description supplies the remaining context an agent needs: ambiguity handling, the relevant alternative tool, and authorization nuances.

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 the baseline is 3, but the description adds meaningful behavior for the workspaceId parameter: a slug may be ambiguous and will be refused with a structured error. The id-or-slug distinction itself is already in the schema.

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 description uses a specific verb and resource: read workspace identity, home, and live capabilities. It distinguishes the operation from adjacent tools by noting workspace_sessions for recent workers and contrasting showing a workspace with loading it.

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?

It gives clear usage context and explicitly routes a related need to workspace_sessions. It also explains that platform admins may show any workspace while loading requires membership, though it does not explicitly compare against workspace_list or whoami.

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