Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

get_pixel

Read-only

Read the composited color of a single pixel at specified X/Y coordinates across all layers, returned as #rrggbbaa for inspection or QA.

Instructions

Read one composited pixel (all layers) at (x, y) as #rrggbbaa.

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

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description still adds real value by disclosing that the value is 'composited (all layers)' and returned as '#rrggbbaa', but it says nothing about out-of-bounds coordinates, transparency handling, or how the file parameter affects which image is sampled.

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?

A single sentence with no padding, and the key fact (composited, all layers) is front-loaded ahead of the coordinates and output format.

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 read tool with no output schema, the description usefully specifies the return format, which the structured fields do not. It is still incomplete on the 'file' parameter and boundary/error behavior, which matter for a coordinate-addressed lookup.

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%, and the bare 'title' fields (X, Y, File) convey nothing. The description clarifies that x and y are pixel coordinates, but the third parameter 'file' (nullable, default null) is never explained, so it does not compensate for the coverage gap.

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 and resource: 'Read one composited pixel (all layers) at (x, y)'. The singular 'one' plus 'composited (all layers)' implicitly separates it from batch siblings like get_pixels and from editor-state tools, though no sibling is named.

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

Usage Guidelines3/5

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

Usage is only implied by 'one pixel' – an agent can infer this is for sampling a single coordinate rather than bulk reads, but there is no explicit when-to-use, when-not-to-use, or named alternative such as get_pixels.

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