Skip to main content
Glama

set_char

Places one character at a specified 0-based (x, y) cell on an ASCII/braille canvas, enabling precise pixel-level artwork edits.

Instructions

Place a single character at a cell. Coordinates are 0-based; (0,0) is top-left.

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>",
      "char": "<char>"
    },
    "name": "set_char"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
charYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/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, yet it does not say whether an existing character at that cell is overwritten, what happens for out-of-bounds coordinates, whether a canvas must already exist, or what the tool returns. Only the coordinate convention is disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/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 coordinate convention. Nothing is redundant or padded.

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?

For a simple 3-parameter mutation with no annotations and no output schema, the definition covers the essentials but omits overwrite behavior and bounds handling, which an agent needs to call it safely.

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 must compensate, and it does explain the coordinate origin and 0-based indexing for x and y. However, the char parameter (a single character) is left entirely to the schema's minLength/maxLength constraint, with no note on multi-byte/wide characters or whitespace.

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?

"Place a single character at a cell" names a specific verb (place) and resource (single character / cell), which distinguishes it from bulk text tools like draw_text or shape_text. It stops short of explicitly contrasting with any sibling, so it lands at 4 rather than 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 draw_text, draw_block, or scatter, and no mention of prerequisites such as requiring an existing canvas. Usage is only implied by the verb "place".

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