Skip to main content
Glama

add_layer

Adds a pixel layer to the active Pixelorama project, placing it on top by default or above a specified layer index.

Instructions

Add a pixel layer. By default it goes on top of all layers.

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": "add_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
aboveNoIndex of the layer to put the new one above

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It usefully reveals the default z-order placement ('By default it goes on top of all layers'), but says nothing about whether the layer lands in the selected cel, whether the name is auto-generated, reversibility, or what the call returns for a mutation tool.

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 action and followed by the default behavior; nothing is wasted. It is on the thin side, but no sentence is filler.

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?

This is a mutation tool with no annotations and no output schema, and one of two parameters (`name`) is undocumented in both schema and description. For an agent to call it confidently, more detail on the created layer and the naming parameter would be needed.

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 50%: `above` is documented in the schema, while `name` is documented nowhere. The description partially compensates by explaining the default when `above` is omitted (top of stack), but adds no meaning for `name`.

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?

"Add a pixel layer" names a specific verb and resource, which distinguishes it from draw_pixels and fill_rect (which modify pixels) and from add_frame (a different container type). It stops short of explicitly contrasting with those siblings, 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 statement of when to use this versus add_frame, select_cel, or draw_pixels, and no prerequisites mentioned. The only contextual hint, default stacking at the top of the layer list, is a behavioral fact rather than usage guidance.

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