Skip to main content
Glama

ai_modeling_canvas_session_get

Read-only

Retrieve a creative planning session by its ID to review stored Canvas planning data and continue work on images, 3D models, or textures.

Instructions

Read a creative planning session.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "ai_modeling_canvas_session_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral detail beyond the word 'Read'—it does not say what a session contains, what happens if the ID is invalid, or how open-world access affects the call.

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 definition is a single front-loaded sentence with no redundant wording. It is terse, but terseness here is a completeness issue rather than a conciseness problem.

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

Completeness2/5

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

For a simple read-only getter, the annotations cover safety and the schema covers the input shape, but the description leaves out the session's return content, error behavior, and how this differs from adjacent canvas/session getters. With no output schema, the description should carry more of that burden.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the sole required parameter, sessionId, and the description never explains what the ID identifies, where to obtain it, or its accepted format. The schema supplies pattern and length constraints but no semantic description, so the description only weakly implies that a session identifier is needed.

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 verb 'Read' and resource 'creative planning session' make the core operation clear. However, the description does not distinguish this getter from sibling session tools such as ai_modeling_canvas_session_create or ai_modeling_canvas_session_mode, and 'creative planning session' is less precise than 'canvas session'.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, no mention of alternatives, and no prerequisite such as obtaining a sessionId from a create call. An agent must infer that this is the retrieval call for an existing session.

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

Deploy Server

Other Tools