Skip to main content
Glama

ai_modeling_canvas_session_create

Starts a creative planning session for a specific canvas, letting agents structure canvas-based asset creation and editing workflows.

Instructions

Create 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": {
      "canvasId": "<canvasId>"
    },
    "name": "ai_modeling_canvas_session_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
canvasIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare a non-read-only, open-world, non-destructive operation, so the description only needs to add context such as persistence, prerequisites, or side effects — and it adds none. It doesn't say whether the session is persisted, what state it starts in, or what identifier comes back.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The statement is a single short sentence with no filler, which is structurally clean. Brevity here comes from under-specification rather than efficiency, since key information is simply absent.

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?

This is a mutating creation tool with an undocumented required parameter and no output schema, so the description should carry substantial weight. Instead it provides one generic sentence, leaving the agent without enough to call the tool confidently.

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

Parameters1/5

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

Schema description coverage is 0% for the single required parameter canvasId, so the description should compensate, but it never mentions the parameter or explains that the session is scoped to a specific canvas. The agent learns nothing about the argument's meaning from the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb and a resource ("Create a creative planning session"), so the basic action is clear. However, "creative planning session" is undefined jargon and the definition gives no way to tell it apart from siblings such as ai_modeling_canvas_create or ai_modeling_canvas_session_get.

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 guidance on when to use this versus ai_modeling_canvas_create, ai_modeling_canvas_from_template, or the other session tools. The agent must guess the intended entry point from the tool name alone.

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