Skip to main content
Glama

ai_modeling_canvas_sessions

Read-only

List all creative planning sessions associated with a specific Canvas to review or resume AI modeling work. Provide the canvas ID to retrieve sessions.

Instructions

List creative planning sessions for a Canvas.

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

Input Schema

NameRequiredDescriptionDefault
canvasIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds no behavioral context beyond that: nothing about pagination, ordering, result limits, whether an empty list is returned for unknown canvases, or what a "session" contains.

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?

A single short sentence with the resource and scope front-loaded and zero filler. It is efficient, though the brevity comes at the cost of specification rather than because nothing more needed saying.

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?

With no output schema, no annotation-derived return info, and an undocumented required parameter, the description should explain what is returned and any paging behavior. It supplies none of this, leaving the agent unable to predict results from a call.

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?

There is one parameter at 0% schema description coverage; the schema only supplies a regex pattern and length bounds but no meaning. The phrase "for a Canvas" hints that canvasId identifies the parent canvas, but the description never explains the identifier format or how to obtain it, so it barely compensates for the coverage gap.

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 gives a verb plus resource ("List creative planning sessions") scoped to a Canvas, which is more than a tautology. However, "creative planning sessions" is an unusual, undefined resource and nothing distinguishes it from sibling list-like tools such as ai_modeling_canvas_events or ai_modeling_canvas_batches, so an agent cannot confidently route between them.

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 tool versus alternatives, no preconditions (e.g., whether the canvas must be owned/shared with the caller), and no exclusions. The agent must infer all selection logic from the 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