Skip to main content
Glama

erase

Clear a single cell on the ASCII/braille canvas by setting it back to a space, removing unwanted characters at specific coordinates.

Instructions

Clear a single cell (set it back to a space).

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

Input Schema

NameRequiredDescriptionDefault
xYes
yYes

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 burden and does not meet it. It does not say whether out-of-range coordinates error or are ignored, what coordinate origin and units apply, whether the operation is undoable, or what the tool 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?

One short sentence with no wasted words, and the effect (setting the cell to a space) is front-loaded right after the action. It is efficient, though the parenthetical could have been spent on coordinates instead.

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 mutation tool with no annotations, no output schema, and two completely undocumented parameters, the description is too thin. Coordinate semantics and failure behavior are exactly the gaps an agent needs filled here.

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%, so the two required parameters x and y are documented nowhere. The description mentions "a single cell" but never maps x/y to coordinates, states their origin, bounds, or units, so an agent must guess what integers mean.

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?

"Clear a single cell (set it back to a space)" gives a specific verb (clear) plus the exact resource (one cell) and even states the resulting state, which implicitly separates it from the whole-canvas sibling clear_canvas. It stops short of naming that sibling explicitly, so the differentiation is inferred rather than stated.

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?

The description never says when to reach for erase versus clear_canvas or set_char, nor does it state any prerequisite or side condition. The words "single cell" carry all the scoping information an agent gets.

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