Skip to main content
Glama

spriteship

by com.spriteship
OverviewDiscussionsAdmin

Arrange, align, and fit collection items

reprocess_asset

FREE and SYNCHRONOUS (no jobId — do not poll), no AI. Rebuild a staged, tileset, or terrain collection's presentation layout: anchor chooses the shared fixed point and cellOffsets apply per-item nudges. Modern manifest revisions are recomposed from their independent item PNGs and are never re-sliced; legacy staged and tileset revisions retain the source-sheet re-cut path, where cellInset can remove separator bleed. For a manifest revision, fitItemIndices makes those items fill their shared cell as much as possible while preserving aspect ratio. Legacy terrain must be upgraded to independent items first. Omitted fields keep the revision's current values; send cellOffsets:[] or cellInset:0 to clear. Returns a grid summary; call get_asset afterwards for fresh presigned tile URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anchorNoWhere each sprite is placed inside its cell. "bottom-middle" is the default for sprites that stand on the ground.
assetIdYesAsset id or slug (staged, tileset, or manifest-backed terrain).
cellInsetNoLegacy source sheets only: pixels shaved off every side of each cell to drop neighbouring bleed (0-32). Ignored for independent-item manifests. Pass 0 to clear.
cellOffsetsNoPer-cell pixel nudges, in tile-index order. Pass [] to clear all nudges.
iterationIdYesCollection revision (iteration) id to arrange.
fitItemIndicesNoIndependent-item manifests only: itemIndex values to fit to the shared cell while preserving aspect ratio. This is a one-shot operation; omitted items keep their saved size.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / assetId / description
      Previous value: -"Asset id or slug (tileset or staged)."New value: +"Asset id or slug (staged, tileset, or manifest-backed terrain)."
    • changedInput schema / properties / cellInset / description
      Previous value: -"Pixels shaved off every side of each cell, to drop neighbouring bleed (0-32). Pass 0 to clear."New value: +"Legacy source sheets only: pixels shaved off every side of each cell to drop neighbouring bleed (0-32). Ignored for independent-item manifests. Pass 0 to clear."
    • addedInput schema / properties / fitItemIndices
      Added value: +{
+  "description": "Independent-item manifests only: itemIndex values to fit to the shared cell while preserving aspect ratio. This is a one-shot operation; omitted items keep their saved size.",
+  "items": {
+    "minimum": 0,
+    "type": "integer"
+  },
+  "maxItems": 256,
+  "type": "array"
+}
    • changedInput schema / properties / iterationId / description
      Previous value: -"Revision (iteration) id to re-cut."New value: +"Collection revision (iteration) id to arrange."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false and openWorldHint=true, but the description adds crucial behavioral context: the operation is synchronous and free, modern manifest revisions are never re-sliced, legacy paths retain source-sheet re-cutting, fitItemIndices is one-shot, omitted fields preserve current values, and cellOffsets:[]/cellInset:0 clear values. It also tells the agent to call get_asset afterwards. This goes well beyond the annotations and makes the side effects and return behavior clear.

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?

The description is dense but every sentence earns its place: sync/free status, main operation, per-revision path differences, legacy prerequisites, field semantics, clearing semantics, and follow-up call. The most important operational facts (FREE, SYNCHRONOUS, no polling) are front-loaded. It is long, but the tool has real complexity to convey.

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

Completeness5/5

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

For a 6-parameter synchronous tool with no output schema, the description covers the operation, the revision-dependent behaviors, the legacy upgrade prerequisite, clearing semantics, and the recommended follow-up call. There is no obvious missing piece an agent would need to safely invoke it or interpret the flow.

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 coverage is 100%, so params are already documented. The description adds meaning beyond the schema by explaining how parameters interact: anchor chooses the shared fixed point, cellOffsets apply per-item nudges, cellInset removes legacy separator bleed, fitItemIndices makes items fill their shared cell while preserving aspect ratio, and omitted fields keep current values. It doesn't enumerate every enum value, but the schema already does that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource: 'Rebuild a staged, tileset, or terrain collection's presentation layout', and clearly differentiates itself from siblings like animate_asset, fix_asset_seams, or revise_asset by describing the layout/arrangement operation. It names the key dimensions (anchor, cellOffsets, cellInset, fitItemIndices) and distinguishes modern manifest revisions from legacy revisions, so an agent can identify the tool's unique role.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance: 'FREE and SYNCHRONOUS (no jobId — do not poll)', 'Legacy terrain must be upgraded to independent items first', and 'call get_asset afterwards for fresh presigned tile URLs'. It also states what not to expect (no AI) and how to clear fields, leaving little ambiguity about when this tool is appropriate.

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

All spriteship toolsInspect
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