spriteship

Get export download command

get_export_command

Read-onlyIdempotent

Build the authenticated download URL + a ready-to-run curl line for a zip export (character engine bundle, asset bundle, or map bundle). Run the curl in your own shell — zips are multi-MB binaries and must not be passed through the model. Phaser character exports may select size 512, 256, 128, or 64; the selected sheet/atlas pairs keep canonical size-agnostic filenames. Sparrow XML is character-only: preserve the bundle's Sparrow prefixes and multisparrow assetPath routing. This tool exports whole characters, not a dashboard single-animation selection. Requires SPRITESHIP_API_KEY to be set in that shell.

Input Schema

TableJSON Schema

Name	Required	Description
`size`	No	Phaser character exports only — narrow the zip to one downscale variant. Godot, Unity, GameMaker, Unreal and Sparrow XML use full-resolution source frames; omit size for them.
`engine`	Yes	Target engine. "fnf" is characters only and emits Sparrow PNG/XML plus character JSON. "tiled" is maps only; sprites have no Tiled emitter. "unreal" is beta Paper2D artwork/flipbook import, not automatic gameplay or native-engine certification.
`target`	Yes	What to export.
`entityId`	Yes	Character id, asset id/slug, or map id.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 14, 2026

changedInput schema / properties / engine / description

Previous value: -"Target engine. \"tiled\" is maps only; sprites have no Tiled emitter. \"unreal\" is beta Paper2D artwork/flipbook import, not automatic gameplay or native-engine certification."New value: +"Target engine. \"fnf\" is characters only and emits Sparrow PNG/XML plus character JSON. \"tiled\" is maps only; sprites have no Tiled emitter. \"unreal\" is beta Paper2D artwork/flipbook import, not automatic gameplay or native-engine certification."

changedInput schema / properties / engine / enum

Previous value: -[
-  "phaser",
-  "godot",
-  "unity",
-  "gamemaker",
-  "unreal",
-  "tiled"
-]New value: +[
+  "phaser",
+  "godot",
+  "unity",
+  "gamemaker",
+  "fnf",
+  "unreal",
+  "tiled"
+]

changedInput schema / properties / size / description

Previous value: -"Phaser character exports only — narrow the zip to one downscale variant. Godot, Unity, GameMaker and Unreal use full-resolution source frames."New value: +"Phaser character exports only — narrow the zip to one downscale variant. Godot, Unity, GameMaker, Unreal and Sparrow XML use full-resolution source frames; omit size for them."

Changed3 schema fields changedSep 9, 2026

changedInput schema / properties / engine / description

Previous value: -"Target engine. \"tiled\" is maps only; sprites have no Tiled emitter."New value: +"Target engine. \"tiled\" is maps only; sprites have no Tiled emitter. \"unreal\" is beta Paper2D artwork/flipbook import, not automatic gameplay or native-engine certification."

changedInput schema / properties / engine / enum

Previous value: -[
-  "phaser",
-  "godot",
-  "unity",
-  "gamemaker",
-  "tiled"
-]New value: +[
+  "phaser",
+  "godot",
+  "unity",
+  "gamemaker",
+  "unreal",
+  "tiled"
+]

changedInput schema / properties / size / description

Previous value: -"Phaser character exports only — narrow the zip to one downscale variant. Godot, Unity, and GameMaker always use full-resolution source frames."New value: +"Phaser character exports only — narrow the zip to one downscale variant. Godot, Unity, GameMaker and Unreal use full-resolution source frames."

Changed1 schema field changedAug 20, 2026

changedInput schema / properties / size / description

Previous value: -"Characters only — narrow a phaser zip to one downscale variant."New value: +"Phaser character exports only — narrow the zip to one downscale variant. Godot, Unity, and GameMaker always use full-resolution source frames."

First observedAug 14, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already mark the tool read-only, open-world, idempotent, and non-destructive, which is consistent. The description adds substantial behavioral context beyond those annotations: the need to execute curl externally, the API key requirement, size-variant filename behavior, Sparrow prefix routing, and the whole-character scope. It fully discloses what the agent must know before invoking it.

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 front-loaded with the core outcome and then delivers dense, high-value constraints without filler. Every sentence contributes operational or scoping information an agent needs, from shell execution to engine-specific export behavior. It earns its length through content density rather than wordiness.

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?

With no output schema, the description correctly explains what the tool returns: a download URL and a curl command line. It also covers prerequisites, export scope, engine-specific restrictions, and filename behavior. Nothing essential for correct invocation appears to be missing.

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 100%, so the baseline is 3 even without additional parameter detail. The description adds meaningful nuance beyond the schema, such as size-agnostic canonical filenames for Phaser sheet/atlas pairs and Sparrow prefix/multisparrow assetPath routing rules. It effectively complements the structured parameter descriptions.

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 uses a specific verb and resource: it builds an authenticated download URL and ready-to-run curl line for zip exports. It clearly scopes the tool to character, asset, and map bundles, and distinguishes it from single-animation dashboard exports. The behavior is unambiguous even among many sibling tools.

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?

The description gives explicit operational guidance: run the curl in your own shell, requires SPRITESHIP_API_KEY to be set, and warns that multi-MB zips must not be passed through the model. It also clarifies that this exports whole characters rather than a single animation, but it does not explicitly name sibling alternatives like get_ui_pack_export_command.

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

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