Skip to main content
Glama

draw_rect

Draw a rectangle on an ASCII/braille canvas by specifying position, width, and height; enable filled mode to create a solid block or leave it off for an outlined border.

Instructions

Draw a rectangle. Set filled=true to fill it, otherwise only the border is drawn.

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

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
charNo#
widthYes
filledNo
heightYes

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?

No annotations are supplied, so the description carries the full behavioral burden. It discloses that filled toggles border-only versus solid rendering, but says nothing about coordinate origin, behavior when the rectangle exceeds canvas bounds, whether a canvas must pre-exist, or what the operation returns.

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?

Two short sentences, front-loaded with the core action and followed by the one non-obvious flag. Nothing is wasted, though the second clause could have been used to cover more of the undocumented parameters.

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 six-parameter mutation tool with no annotations and no output schema, the description is thin. It covers one of six parameters and omits coordinate semantics, canvas requirements, and error or boundary behavior.

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 description coverage is 0% across six parameters, so the description must compensate and largely does not. Only filled is explained; x, y, width, height, and especially char (the drawing character, defaulting to '#') receive no meaning beyond their self-evident names.

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 rectangle.' An agent immediately knows the operation and primitive being created. It does not distinguish this from siblings like draw_block or draw_line, but the primitive itself is unambiguous.

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 draw_rect over draw_block, draw_line, or other drawing siblings, nor any stated prerequisites such as needing an existing canvas. The only conditional given, filled=true, is parameter usage rather than tool selection guidance.

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