Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

get_pixels

Read-only

Read a composited pixel region as a grid of #rrggbbaa strings to inspect what the canvas looks like now; keep regions within 4096 px or export larger areas.

Instructions

Read a composited pixel region as a grid of #rrggbbaa strings — the AI feedback loop for 'what does the canvas look like now'. Capped at 4096 px; use a smaller region or export for larger areas.

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

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
fileNo
widthYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuine value beyond that: 'composited' signals that layers are flattened and the return is a string grid, plus a hard 4096 px cap. It does not discuss cost/latency for large reads or behavior when the region extends past the canvas edge.

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 sentences, front-loaded with what is returned and what it is for, then the limit and the escape hatch. No filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-format burden and does so ('#rrggbbaa strings'); the cap and fallback are also present. The gaps are the undocumented file parameter and unspecified grid ordering or out-of-bounds behavior, which are modest for a read tool.

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% across five parameters, and the description only implicitly covers the x/y/width/height region semantics and the size cap. The 'file' parameter is never mentioned in either place, leaving its role (which document the pixels come from) entirely unexplained.

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 states a specific verb (Read) and resource (a composited pixel region) and pins down the return shape as a grid of #rrggbbaa strings. It stops short of differentiating itself by name from the singular get_pixel or the broader look tool, but the 'region' framing makes the scope clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete usage context — 'the AI feedback loop for what does the canvas look like now' — and a boundary condition: capped at 4096 px, so use a smaller region or export for larger areas. It never names a specific alternative tool to route to, which keeps it from a 5.

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

Deploy Server

Other Tools