Skip to main content
Glama

Read Playground canvas

playground_canvas_read
Read-onlyIdempotent

Read the current node graph and revision for a Berrys Canvas Playground workflow. Returns the graph, current revision and Playground URL with a canvas preview.

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

Input Schema

NameRequiredDescriptionDefault
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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered by structured data. The description adds only the return contents (graph, revision, Playground URL, preview), which an output schema likely already covers; it says nothing about size limits, pagination, or failure when a project has no canvas.

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?

Two short sentences, front-loaded with the operation and followed by return contents; nothing is padding. The second sentence partially restates the first, but it does add value by naming the artifacts returned.

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-parameter read with full annotations and an output schema, the definition covers what it does and what comes back. Missing only edge-case behavior (no canvas yet, permission requirements) which is minor at this complexity.

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% and the single projectId parameter is fully described there, including where to obtain it, so the description carries no additional parameter burden. Baseline 3 applies since no further meaning is added.

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 resource ('current node graph and revision') scoped to a Berrys Canvas Playground workflow, and names the returned artifacts. It does not distinguish itself from siblings like playground_canvas_snapshots_list or playground_context_current, so an agent must infer which read it wants.

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?

Usage is only implied by the word 'current' — read live state rather than a snapshot or prior context. No explicit when-to-use, when-not-to-use, or pointer to a sibling alternative is given.

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.