Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

measure_padding

Read-only

Measure transparent padding around sticker content to obtain bounding box, per-side padding, fill ratio, and opaque color count for read-only QA.

Instructions

Measure the transparent 'sticker' padding around the content: content bounding box, per-side padding (left/right/top/bottom), fill ratio, and distinct opaque color count. Read-only. Headless: pass file.

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

Input Schema

NameRequiredDescriptionDefault
fileNo

Output Schema

NameRequiredDescriptionDefault
emptyNo
canvasNo
contentNo
paddingNo
fillRatioNo
colorCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior3/5

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

'Read-only' duplicates the readOnlyHint=true annotation, so it earns no credit. The description does add genuine behavioral context by clarifying what counts as 'padding' (transparent margin around opaque content) and what is computed (bounding box, per-side padding, fill ratio, color count), but says nothing about cost, failure modes, or behavior when the file argument is omitted.

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 tight sentences, front-loaded with the result set before the invocation note. Every clause carries information; no filler or restated boilerplate beyond the brief 'Read-only' line.

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?

An output schema exists, so return values need no explanation, and readOnlyHint covers the safety profile. The only meaningful residual gap is the semantics of the optional `file` parameter, which is hinted at but not fully specified.

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?

The single `file` parameter has 0% schema description coverage and no type-level explanation, so the description must carry it. 'Headless: pass ``file``' does convey that the parameter is conditional on headless operation, which is real added meaning, but it never states the accepted path/format or what happens when it is null.

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?

Names a specific verb (measure) plus the resource (transparent 'sticker' padding around the content) and enumerates the four things it returns, so an agent knows exactly what operation this performs. It does not explicitly contrast itself with any sibling, but the 'measure' framing clearly separates it from the mutation tools like add_glow or adjust_brightness_contrast.

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?

'Headless: pass ``file``' gives one concrete invocation context, and 'Read-only' signals it is safe to call speculatively. There is no explicit when-to-use versus when-not guidance, nor any suggestion of alternatives for related measurement tasks, so usage is only implied.

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