Skip to main content
Glama

new_canvas

Start a new ASCII drawing by creating a blank canvas with the specified character width and height; use it before adding artwork.

Instructions

Start a fresh ASCII canvas of the given size (in characters). Call this before drawing a new piece.

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": {
      "width": "<width>",
      "height": "<height>"
    },
    "name": "new_canvas"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. 'Start a fresh' implies an initially blank canvas, but it never states what happens to any existing canvas content, whether the call is destructive, or whether there is a default size. Units are disclosed, which is genuinely useful.

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, action first, guidance second, with no filler. Every sentence adds information an agent needs.

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

Completeness4/5

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

For a two-parameter tool with no output schema and no annotations, the definition covers purpose, units, and call ordering, which is close to what an agent needs to invoke it. The remaining gap is the lack of any statement about existing canvas content being replaced.

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 0%, so the description must compensate, and it does partially by clarifying that width/height are measured in characters rather than pixels. It adds nothing about the two dimensions individually or the interaction between them, leaving the bounds entirely to the schema's min/max.

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 fresh ASCII canvas') plus the scalar meaning of the size ('in characters'). It does not explicitly differentiate itself from clear_canvas or resize_canvas, which are the closest siblings, so the agent must infer the distinction.

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

Usage Guidelines4/5

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

'Call this before drawing a new piece' gives explicit sequencing guidance for the intended workflow. It stops short of stating when NOT to use it (e.g., when an existing canvas should be cleared instead of replaced).

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