Skip to main content
Glama

clear_cel

Erase all pixels in one cel—a layer within a frame—by specifying the frame and layer, clearing that artwork while leaving other layers intact.

Instructions

Erase every pixel of one cel (a layer in a frame).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clear_cel"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameNoFrame index, from 0. Defaults to the current frame
layerNoLayer index, 0 is the bottom layer. Defaults to the current layer

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key trait that the operation wipes ALL pixels in the cel rather than a region. However, it omits reversibility/undo, what happens if the target cel does not exist, and any return or error behavior for a destructive write.

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?

A single sentence, front-loaded with the action and scope, with the parenthetical definition of 'cel' earning its place by disambiguating the resource. No filler.

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 simple and both optional parameters are fully documented in the schema, so the description is nearly sufficient. For an irreversible destructive operation with zero annotation coverage, one clause on undo-ability or on requiring an existing cel would close the remaining gap.

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 coverage is 100% and both frame and layer already carry descriptions including zero-based indexing and default-to-current behavior. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb+resource ('Erase every pixel of one cel') and even disambiguates what a cel is ('a layer in a frame'), which separates it from fill_rect and draw_pixels. It stops short of naming a sibling tool or contrasting behavior explicitly, so it is clear but not fully differentiated.

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 at all: nothing says whether to use this instead of fill_rect with a background color, or that it applies only to an existing cel. The agent must infer usage purely from the verb 'erase'.

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