Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

get_tilemap_info

Read-only

Read a tilemap layer to retrieve tile size, tileset length, cel grid dimensions, pixel position, and tile-index grid for inspection or validation; supports headless files.

Instructions

Read a tilemap layer: tile size, tileset length, and the cel's grid size, pixel position, and tile-index grid (tiles as rows of columns, flip flags stripped; capped at 64x64 with truncated set). Read-only. Headless: pass file.

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": {
      "layer": "<layer>"
    },
    "name": "get_tilemap_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
frameNo
layerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description still adds meaningful behavior beyond that: the grid is capped at 64x64 with a ``truncated`` flag, and flip flags are stripped from tile indices. Those are exactly the surprises an agent needs warned about. It does not mention error behavior for an invalid layer name.

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?

Three short sentences, front-loaded with what is returned, then the truncation caveat, then the headless rule. Density is high and nothing is padding, though the backtick-heavy phrasing makes it slightly harder to scan than plain prose.

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?

With no output schema, the description usefully describes the return shape and the truncation contract, which is the most important completeness gap it could have filled. However, the two undocumented parameters (layer, frame) remain opaque, so an agent knows what it will get but not fully how to ask for it.

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 description carries the full burden, and it only explains ``file`` (as the headless path). The required ``layer`` parameter and ``frame`` (defaulting to 1) receive no explanation of accepted form — name vs index, 0- vs 1-based — leaving the required argument ambiguous.

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 names a specific verb and resource ('Read a tilemap layer') and enumerates exactly what comes back: tile size, tileset length, cel grid size, pixel position, and the tile-index grid. That is enough for an agent to distinguish it from a write-oriented sibling like create_tilemap_layer, though no sibling is named explicitly.

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?

It states 'Read-only' and gives one concrete usage rule: 'Headless: pass ``file``.' That is a real context cue, but there is no guidance on when to prefer this over other inspection tools (e.g. get_sprite_info) or what happens when the wrong layer is supplied. Usage is implied rather than prescribed.

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