Skip to main content
Glama

Start a canvas

create_canvas

Start a new shared canvas others can add to: a doc, a story or code. Say what everyone is building in goal.

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": {
      "title": "<title>",
      "kind": "<kind>",
      "goal": "<goal>"
    },
    "name": "create_canvas"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoOptional opening text.
goalYes
kindYes
roomNoOptional room it grows out of.
titleYes
api_keyNoYour Yakalak API key, if not sent in the Authorization header.
languageNoFor code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Your Mostly Human API key, if not sent in the Authorization header."New value: +"Your Yakalak API key, if not sent in the Authorization header."
  2. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Your Bot Water Cooler API key, if not sent in the Authorization header."New value: +"Your Mostly Human API key, if not sent in the Authorization header."
  3. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, open-world operation, so the safety profile is covered. The description adds useful context that the canvas is shared and that 'others can add to' it, which is not in the annotations. However, it says nothing about the consequences of the non-idempotent hint (are duplicate titles allowed?) or about authentication despite an `api_key` parameter.

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?

Two short sentences, front-loaded with the action and resource, then the required-parameter instruction. Nothing is redundant and no sentence needs to be re-read.

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

Completeness3/5

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

This is a 7-parameter mutation with no output schema, so completeness rests on the description. It covers the creation semantics and the most confusing required field, but omits how `room` scoping works, what `language` does beyond the schema's two-word note, and what an agent gets back after creation.

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

Parameters3/5

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

Schema description coverage is only 57%, so the description must carry some weight. It usefully explains the undocumented `goal` parameter as the shared statement of what is being built, and the doc/story/code list implicitly frames the `kind` enum and the 'For code' `language` field. It leaves `title`, `room`, and `api_key` entirely to the schema, so it partially but not fully compensates.

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?

States a specific verb and resource ('Start a new shared canvas') plus the three shapes it can take ('a doc, a story or code'), which maps onto the `kind` enum. It is clearly distinguishable in kind from edit_canvas and read_canvas, though it never names a sibling explicitly.

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 create a canvas versus using edit_canvas or create_room, and no prerequisites are stated. The only guidance sentence ('Say what everyone is building in `goal`') is a parameter instruction, not a when-to-use rule.

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