Skip to main content
Glama
Godot MCP - Full Control
by cxb2523

game_canvas_draw

Draw and clear 2D lines, rectangles, circles, polygons, and text in Godot to create or update canvas visuals via the MCP server.

Instructions

2D drawing: line/rect/circle/polygon/text/clear

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": {
      "action": "<action>"
    },
    "name": "game_canvas_draw"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd point {x,y}
fromNoStart point {x,y}
rectNoRectangle {x,y,w,h}
textNoText to draw
colorNoDraw color {r,g,b,a}
widthNoLine width. Default: 2
actionYesAction: line, rect, circle, polygon, text, clear
centerNoCenter point {x,y}
filledNoFill shape. Default: true
pointsNoPolygon points [{x,y},...]
radiusNoCircle radius
fontSizeNoText font size. Default: 16
positionNoText position {x,y} (baseline, for text)
parentPathNoParent node path for draw node

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it discloses no behavior at all: no indication that drawing is a write operation, whether it needs a target draw node, whether 'clear' wipes prior content, or whether changes persist. It also never explains the parentPath draw-node targeting, which materially affects how the tool behaves.

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?

It is a single compact line with zero filler and is front-loaded with the tool's purpose. The terseness also causes under-specification, but in terms of word economy nothing is wasted.

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 14 parameters, nested point objects, no annotations, and no output schema, a one-line description is not enough to let an agent safely compose drawing calls or understand the side effects of 'clear'. Read format, coordinate system, and draw-node targeting are all left entirely to the schema.

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 100%, including per-parameter descriptions and defaults for width, filled, and fontSize, so the schema already does the heavy lifting. The description's action list merely repeats the action enum from the schema and adds no meaning about parameter combinations or format coercion.

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?

It names a specific verb and resource ('2D drawing') and enumerates the exact operations (line/rect/circle/polygon/text/clear), which the schema confirms. It does not distinguish itself from closely related siblings such as game_canvas, game_debug_draw, or game_shape_2d, so it stops short of a 5.

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 alternative tools or when not to use it. The word 'clear' hints at a destructive operation, but no conditions, prerequisites, or alternatives are stated.

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