Skip to main content
Glama

draw_line

Draw a straight line of a chosen character between two coordinate points on an ASCII canvas. Specify start and end coordinates plus an optional character to render the line.

Instructions

Draw a straight line of a character between two points.

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": {
      "x1": "<x1>",
      "y1": "<y1>",
      "x2": "<x2>",
      "y2": "<y2>"
    },
    "name": "draw_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
x1Yes
x2Yes
y1Yes
y2Yes
charNo*

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.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 behavioral burden and comes up short. It does not state that the operation mutates the canvas, whether existing characters are overwritten, how out-of-bounds coordinates are clipped, or what the call returns. For a drawing mutation on a 1000-unit coordinate space, those omissions matter.

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. It is efficient, though the brevity is achieved partly by omitting rather than by compressing genuinely covered information.

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?

The tool is low-complexity with a flat five-parameter schema and no output schema, so a short description is defensible. Still, with no annotations anywhere, the definition leaves the mutation semantics and the char default unwritten, which is a real gap for an agent invoking it blindly.

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 has to compensate, and it partially does: 'between two points' establishes that the four coordinates form an endpoint pair, and 'of a character' explains the optional char parameter. It adds nothing about coordinate bounds, endpoint ordering, or how a single character interacts with the grid, so the gap is only partly filled.

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 specific verb and resource: 'Draw a straight line of a character between two points.' That is concrete enough that an agent can distinguish it from siblings like draw_rect or draw_block by the shape drawn, although it never names those alternatives.

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 when-to-use guidance, no mention of prerequisites such as an existing canvas, and no routing to alternatives such as draw_rect or fill_gradient. The agent must infer all of that from the tool name alone.

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