Tokenrip

Read open browser view

workspace_view_context

Read-onlyIdempotent

Read the browser tab paired to your agent key in this workspace (the person opened your load browserLink). Use this before deictic edits such as “update paragraph two”. state is disconnected when no tab follows you.

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

Input Schema

Name	Required	Description	Default
`workspaceId`	Yes	The workspace: its id or its slug.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 24, 2026

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)$"

First observedOct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description contributes beyond that: it explains the pairing premise (a human opened the browserLink for this agent key) and the disconnected state when no tab is attached, which is exactly the kind of runtime behavior an agent needs. Return-shape detail is legitimately omitted because an output schema exists.

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?

Three short sentences, with the core action and scoping front-loaded and the disconnection caveat placed last where it belongs. The parenthetical '(the person opened your load browserLink)' is terse to the point of being slightly opaque, but it carries real information rather than padding.

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?

For a single-param read tool with full annotations, an output schema, and a documented precondition, the description supplies everything an agent needs to decide to call it and to interpret a disconnected result. The only remaining ambiguity is who/what populates browserLink, which is resolvable from the sibling workspace_load.

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?

There is a single parameter with 100% schema description coverage ('the workspace: its id or its slug'), so the schema carries the semantics. The description's phrase 'in this workspace' reinforces the scoping but adds no syntax beyond the schema. Baseline 4 applies for a one-param tool whose schema is fully documented.

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 (Read) and a precisely scoped resource: the browser tab paired to this agent key in this workspace. The pairing mechanism (the person opened your load browserLink) further distinguishes it from the sibling workspace_view_open and from workspace_load. It is slightly cryptic about what a 'browserLink' is, but an agent can tell what this returns versus the open sibling.

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 explicit when-to-use guidance: 'Use this before deictic edits such as "update paragraph two"'. It also surfaces a failure condition ('state is disconnected when no tab follows you'), which effectively tells the agent when the tool will not yield data. It does not explicitly contrast with workspace_view_open, so it stops short of a 5.

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.