Skip to main content
Glama

Canvas View Session

aimixer_canvas_view_session
Read-onlyIdempotent

Use when the user asks to show or look at the Canvas, or you need to see its rendered UI/layout, and the app tools capture_view/navigate_view are not listed. Get a short-lived (default 10 minutes, ttl_sec 60-600) read-only viewing link for ONE owned Canvas project. The link opens the same read-only Canvas viewer used by public share links, but only for this project and only until expires_at; it never exposes or creates the owner's permanent share link, cannot edit anything and needs no login. Open view_url in a JavaScript-capable browser tool to look at the project (a fetch-only tool sees an empty page); call again for a fresh link after it expires.

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": {
      "project_id": "<project_id>"
    },
    "name": "aimixer_canvas_view_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttl_secNo
project_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: default 10-minute lifetime, 60-600 TTL bounds, per-project scoping, expiry via expires_at, that it never creates the owner's permanent share link, that it cannot edit, requires no login, and requires a JavaScript-capable browser (fetch-only tools see an empty page). That browser requirement is a critical operational caveat the annotations cannot convey.

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?

Front-loads the trigger, then lifetime, then the viewer's semantics and the browser caveat; every sentence carries information. It is a dense single block rather than structured bullets, which slightly hurts scannability for a description this long.

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?

Even though an output schema exists, the description explains what the returned link is, how long it lasts, and how to consume it; combined with the annotated safety profile and TTL semantics, an agent has everything needed to invoke it correctly.

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 0%, so the description must carry parameter meaning, and it does explain ttl_sec's default and 60-600 range and that project_id must be an owned Canvas project. It does not describe the project_id format or how to discover a valid one, leaving a small gap.

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?

States a specific verb and resource: 'Get a short-lived ... read-only viewing link for ONE owned Canvas project.' It also distinguishes itself from the app-level capture_view/navigate_view tools, so an agent can tell what it delivers versus siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('Use when the user asks to show or look at the Canvas, or you need to see its rendered UI/layout') plus a gating condition ('and the app tools capture_view/navigate_view are not listed'), and tells the agent to call again after expiry.

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.

Resources