Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

set_editor_view

Idempotent

Sets the live Aseprite editor's zoom and/or scroll position to focus the canvas region being edited, letting the artist watch the work area.

Instructions

Live editor only: set the viewport zoom (1.0 = 100%) and/or scroll — e.g. zoom to the region you're about to edit so the artist can watch.

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

Input Schema

NameRequiredDescriptionDefault
zoomNo
scroll_xNo
scroll_yNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and the title; the description adds the genuinely useful behavioral fact that this only applies to a live editor session and that the change is visible to the artist in real time. It does not say what happens in a non-live session (error vs no-op) or whether omitted fields are left untouched.

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?

One tight sentence plus an inline example; the live-editor-only constraint is front-loaded. Slightly wasteful in that the example sentence repeats the zoom meaning already implied by the first half.

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

Completeness1/5

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

For a three-parameter mutation-ish tool with no annotations covering behavior, no output schema, and 0% schema description coverage, the description omits units, coordinate semantics, and failure behavior in non-live sessions. What remains is far short of what an agent needs to call it correctly.

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

Parameters1/5

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

Schema description coverage is 0% across three parameters with opaque names, and the description only glosses 'zoom' (1.0 = 100%). scroll_x/scroll_y have no units, coordinate origin, or null/omit semantics explained anywhere, which leaves the caller guessing for two of three params.

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?

Description states a specific verb+resource ('set the viewport zoom and/or scroll') and scopes it to 'Live editor only', which distinguishes it from the get_editor_state sibling. It doesn't name or contrast any other view-affecting sibling, so it stops short of a 5.

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?

Gives a motivating example ('zoom to the region you're about to edit so the artist can watch') and a hard precondition ('Live editor only'), which implies usage context. There is no explicit when-not guidance, and the alternative of using get_editor_state to discover the current view is left to inference.

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