Nano Studio Pro

Get a sheet's frame rects and animation tags

get_sheet_atlas

Read-only

FREE. For a sheet you own (its generation id): every frame's pixel rect, the per-frame registration, fps, pivot and one animation tag per sequence, as Aseprite JSON that Phaser, Pixi, Godot and Unity import. Ask this instead of measuring gutters in the pixels.

Input Schema

Name	Required	Description
`grow`	No
`clean`	No
`pieces`	No	true = every cell as a trimmed transparent PNG link, with its label. grow, clean: default true.
`generation_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 26, 2026

addedInput schema / properties / clean
```
Added value: +{
+  "type": "boolean"
+}
```
addedInput schema / properties / grow
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / pieces

Added value: +{
+  "description": "true = every cell as a trimmed transparent PNG link, with its label. grow, clean: default true.",
+  "type": "boolean"
+}

First observedSep 17, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already supply readOnlyHint=true; the description adds real context beyond that: it is free, requires ownership of the sheet, and returns an import-ready Aseprite JSON format compatible with Phaser/Pixi/Godot/Unity. It omits anything about size/limits, but for a free read that is minor.

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?

Two tight sentences that are front-loaded: 'FREE.' plus the payload first, then the usage nudge. Every phrase carries information (cost, ownership, payload contents, format targets, alternative) with no filler.

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 does the heavy lifting by describing the returned Aseprite JSON in detail, which is strong. However, the unexplained grow/clean parameters and the trimmed-PNG 'pieces' mode leave gaps an agent cannot resolve from structured fields alone.

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 coverage is only 25% and the description only clarifies generation_id ('its generation id'), leaving grow and clean entirely undefined in both schema and description. With three of four parameters under-explained, the description 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 resource (a sheet's frame rects and animation tags) and enumerates the exact payload: per-frame pixel rect, registration, fps, pivot, and one tag per sequence as Aseprite JSON. An agent understands precisely what it returns, though no sibling tool (e.g. sheet_options) is named for differentiation.

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

Usage Guidelines4/5

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

'For a sheet you own (its generation id)' gives the precondition, and 'Ask this instead of measuring gutters in the pixels' tells the agent when to prefer this over manual parsing. No explicit when-not or named alternative tool, so short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nano Studio Pro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?