Skip to main content
Glama

Open your Playground workspace

playground_canvas_open
Read-onlyIdempotent

Return the authorized project URL focused on selected node IDs. If your host has an in-app browser, open it beside chat and reuse that project tab. Otherwise show the link. This tool does not itself control a browser or prove the user is signed in.

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": {
      "projectId": "<projectId>"
    },
    "name": "playground_canvas_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdsNoIDs of the existing canvas nodes to use for this action.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.

Output Schema

NameRequiredDescriptionDefault
graphYes
revisionYes
canvasUrlYes
projectIdYes
projectNameYes
focusNodeIdsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 behavior, so the bar is lower. The description adds meaningful context by clarifying that the tool 'does not itself control a browser or prove the user is signed in,' which prevents an agent from assuming side effects that do not occur.

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?

The description is three sentences and front-loads the main action. It is efficient, though the second and third sentences focus more on host integration behavior than on when to invoke the tool, slightly diluting the core instruction.

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?

An output schema exists, so return values need not be explained. For a simple read-only tool with two parameters, the description covers the key behavioral caveats (no browser control, no auth proof) and host integration. It is complete enough for an agent to call correctly, though it could be more explicit about tool selection relative to siblings.

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 both parameters fully. The description references 'selected node IDs' and the project URL, but adds no extra syntax, constraints, or edge-case meaning beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description states a specific verb ('Return') and resource ('authorized project URL focused on selected node IDs'), making the core action clear. It does not explicitly differentiate itself from sibling tools like playground_canvas_read, but the intended output is distinct enough for an agent to recognize.

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?

The description gives guidance on what to do with the result ('open it beside chat and reuse that project tab' or 'show the link'), but it does not explain when to call this tool versus alternatives, nor does it state any preconditions or exclusions. Usage is implied rather than explicitly contrasted with sibling tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.