Skip to main content
Glama

game_canvas_draw

Draw 2D shapes and text on a Godot canvas using actions for lines, rectangles, circles, polygons, and text, with optional fill and color. Clear the canvas when needed.

Instructions

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

Input Schema

TableJSON 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
parentPathNoParent node path for draw node
Behavior2/5

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

Without annotations, the description must disclose behavioral traits. It mentions 'clear' as an action but does not describe drawing behavior (e.g., whether lines overlay, if the canvas initially is blank, or if coordinates are relative). This lack of detail hinders accurate expectation.

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?

The description is extremely concise (one sentence) and front-loaded with the main purpose. However, it could be structured slightly better by grouping actions, but overall it is efficient.

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?

Given the tool's complexity (12 parameters including nested objects, no output schema), the description is insufficient. It only lists action types without explaining how to use them, parameter combinations, or expected effects. This leaves the agent guessing about correct usage.

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%, so the schema already documents parameters. The description adds no parameter meaning beyond the list of actions. Baseline 3 is appropriate since the description does not compensate with contextual parameter relationships (e.g., which parameters are required for each action).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: '2D drawing: line/rect/circle/polygon/text/clear'. It enumerates specific actions, distinguishing it from sibling tools like game_canvas or other drawing utilities.

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?

No usage guidance is provided. The description does not indicate when to use this tool versus alternatives, nor does it specify prerequisites or exclusions. The agent must infer usage from the action list alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tugcantopaloglu/godot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server