Skip to main content
Glama

spriteship

by com.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. Requires SPRITESHIP_API_KEY to be set in that shell.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoPhaser character exports only — narrow the zip to one downscale variant. Godot, Unity, and GameMaker always use full-resolution source frames.
engineYesTarget engine. "tiled" is maps only; sprites have no Tiled emitter.
targetYesWhat to export.
entityIdYesCharacter id, asset id/slug, or map id.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • 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."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark it read-only, open-world, idempotent, and non-destructive; the description adds meaningful behavioral context: it returns a command rather than file contents, requires the caller's shell to have SPRITESHIP_API_KEY, and describes engine-specific size behavior and canonical filenames. No contradiction with annotations.

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?

Three sentences with each earning its place: the core purpose, the critical shell-execution warning, the Phaser-specific sizing nuance, and the API key prerequisite. Information is front-loaded and there is no redundancy.

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 clearly states what the tool returns (URL plus curl command) and the environment needed to use it. It is complete enough for an agent to know how to invoke it and what to do with the result.

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

Parameters3/5

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

Input schema covers all four parameters at 100% with descriptions, so the baseline applies. The description adds useful nuance about Phaser-only size options and canonical filenames, but does not need to compensate for schema gaps.

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?

Description uses a specific verb and resource: builds an authenticated download URL plus a ready-to-run curl line for zip exports. It identifies the export types (character, asset, map) and the run-in-shell behavior, which distinguishes it from actual export/download 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?

Clear context: this is for obtaining a curl command to run outside the model, with an explicit warning that multi-MB zips must not be passed through the model. It states the API key prerequisite but does not explicitly name alternatives or when-not-to-use conditions.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, and the descriptions are extremely detailed with cross-references (e.g., animate_asset vs frame_animation vs generate_character_animation). A few pairs like reprocess_asset vs revise_asset could be confused initially, but their descriptions and use cases are explicit enough to prevent misselection.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_project, get_asset, cancel_job). Verbs are imperative and nouns are appropriately singular/plural, making the API predictable and readable.

Tool Count2/5

At 41 tools, the server is far beyond the 15-25 range considered reasonable for most APIs. While the domain is broad (project, assets, characters, animations, jobs, exports, credits), the sheer number creates a heavy surface that may overwhelm agents and suggests the API could be consolidated into higher-level operations.

Completeness4/5

The tool set covers the full creative pipeline: project creation, asset/character generation, animation (both AI and frame-based), revisions, exports, and job management. Minor gaps include lack of delete operations for assets/characters/projects and no listing of all jobs, but these are not critical for the core workflow and are likely intentional for a generative art platform.

Resources