Skip to main content
Glama

ai_modeling_canvas_session_mode

Set a Canvas creative session to automatic or controlled mode so agents can choose how much manual approval each AI modeling step requires.

Instructions

Set the creative session mode.

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>",
      "mode": "<mode>"
    },
    "name": "ai_modeling_canvas_session_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
sessionIdYes

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=false and destructiveHint=false, so the mutation/safety profile is partly covered. The description still adds nothing about whether a mode change is reversible, whether it affects ongoing session state, what openWorldHint=true implies here, or what the response contains — a meaningful gap for a state-changing tool.

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 single sentence is front-loaded and free of filler, but here brevity reflects under-specification rather than efficiency. There is no structure to hang the enum semantics or prerequisites on.

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 two-required-parameter mutation tool with no output schema and zero schema description coverage, the description should explain the mode values and session requirement. It omits both, so an agent cannot confidently invoke it without inspecting the raw enum.

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%, so the description carries the full burden but supplies almost none of it. It vaguely gestures at the "mode" parameter but never explains MODE_AUTO vs MODE_CONTROL semantics, and says nothing about the required sessionId or its format constraints.

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 states a verb ("Set") and an object ("the creative session mode"), so the general action is identifiable. However, "creative session mode" is never defined, and nothing distinguishes this from siblings like ai_modeling_canvas_session_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 call this, no prerequisites (e.g., an existing session), and no indication of when to prefer it over other session tools. The two enum values MODE_AUTO and MODE_CONTROL are not compared or explained, leaving the agent to guess which to choose.

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