Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

adjust_brightness_contrast

Adjust the active cel's brightness and contrast from -100 to 100 while preserving alpha, with one undo step; pass a file for headless edits.

Instructions

Adjust the active cel's brightness and contrast, each -100..100 (0 = unchanged). Alpha is preserved. One undo step. 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": "adjust_brightness_contrast"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
contrastNo
brightnessNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior4/5

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

With only a title annotation and no hint flags, the description carries the burden and does real work: it discloses the accepted range (-100..100), the neutral value (0 = unchanged), that alpha is preserved, and that the operation costs exactly one undo step. That undo/alpha information is behavior an agent cannot get from any structured field. Missing is what happens when values clamp or how the headless file target relates to the active cel.

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?

Four short clauses, front-loaded with the action and target, then range, side effects, and the headless escape hatch. No filler sentences and nothing repeated from the schema.

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?

For a simple three-parameter, no-output-schema adjustment tool this covers range, neutral value, alpha handling, undo cost, and headless invocation — enough for correct invocation. Only the exact semantics of the `file` argument and clamping behavior are left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it largely does: it gives the domain and default semantics for both brightness and contrast and explains the purpose of the otherwise opaque `file` parameter as the headless path. It leaves the type/format of `file` (path vs identifier) unstated, which is the main remaining 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+resource ('Adjust the active cel's brightness and contrast'), which is concrete and distinguishable from a hue/saturation sibling like adjust_hsl. It stops short of explicitly naming the neighboring color tools, so the differentiation is inferred from the parameter names rather than stated.

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 context is implied by 'active cel' plus the headless note ('Headless: pass file'), which does tell an agent how to invoke it outside a GUI context. There is no explicit when-not guidance or pointer to an alternative tool for hue/saturation or other tonal adjustments.

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