Skip to main content
Glama

draw_text

Draws horizontal text at a specified (x, y) position on an ASCII or braille canvas, enabling precise labeling and annotation.

Instructions

Write a line of text horizontally starting at (x, y).

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": {
      "x": "<x>",
      "y": "<y>",
      "text": "<text>"
    },
    "name": "draw_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses direction (horizontal) but not what happens if the text runs past the canvas edge, whether it overwrites existing characters, how multi-character strings are laid out, or whether any rendering step is required afterward. These are material gaps for a drawing mutation.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the brevity reflects under-specification rather than tight editing.

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 three-parameter mutation tool with no annotations, no output schema, and zero schema descriptions, the description is too thin to let an agent call it confidently. Overflow behavior, coordinate units, and relationship to sibling text tools are all missing.

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 coverage is 0%, so the description must define the three parameters. It does clarify that x and y are an origin and that text is drawn rightward, but it never states the coordinate units (character cells vs pixels) or whether (x, y) is the top-left of the text block, leaving the most important ambiguity unresolved.

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?

The description gives a concrete verb and resource ('Write a line of text') plus the origin point, which is enough to distinguish it from drawing primitives like draw_line or draw_rect. It does not, however, distinguish it from the other text tools (banner_text, shape_text), so the differentiation is only partial.

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 choose this over banner_text or shape_text, and no stated preconditions such as needing an existing canvas. The agent must infer the choice purely from the word 'horizontally'.

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