Skip to main content
Glama

generatePose

Re-pose an existing sprite into a new target pose while preserving the character, taking a source image (URL or base64), a pose name (or "Other" with a free-text description), and an optional n (1-4) for how many variations to produce. Only works with sprite image types (not icons, screenshots, etc.). The job result is an array of pose results, each containing the generated image url, the pose and description used, and a suggested motion_prompt tuned for that pose. Credits are held when the job is accepted and refunded if it fails or is cancelled; the charge scales with the number of images generated. This is typically the first step before animating: call generatePose to set the character's pose, then feed the result (and its suggested motion_prompt) into animateSprite for the best animation quality; use rotateSprite instead when you want to change the camera angle rather than the pose. Pass an optional request_id to tag the results so you can locate them later via listGenerations (type spritesheet). Async generation job: returns {id, status} - poll getApiJob (job and credit contract: see the server instructions).

Credits: This endpoint consumes 0.5 credits per result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestBodyYesPayload for generating a new pose for an existing sprite

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / requestBody / properties / request_id / description
      Previous value: -"Optional client-provided identifier, unique per request. Re-sending the same request_id returns the existing job instead of generating again. Also usable with the results endpoint."New value: +"Optional client-provided identifier, unique per request. Re-sending the same request_id returns the existing job instead of generating again. Also usable as the request_id filter of listGenerations."
  2. Changed4 schema fields changed
    • removedInput schema / properties / requestBody / properties / augment_prompt / default
      Removed value: -true
    • changedInput schema / properties / requestBody / properties / augment_prompt / description
      Previous value: -"Augment the prompt behind the scenes. Disable to have more control."New value: +"Augment the prompt behind the scenes. Disable to have more control. Default: true."
    • removedInput schema / properties / requestBody / properties / n / default
      Removed value: -1
    • changedInput schema / properties / requestBody / properties / n / description
      Previous value: -"Number of pose variations to generate (1-4)."New value: +"Number of pose variations to generate (1-4). Default: 1."
  3. Changed1 schema field changed
    • changedInput schema / properties / requestBody / properties / request_id / description
      Previous value: -"Optional client-provided identifier for this request. Use this to retrieve results later via the results endpoint."New value: +"Optional client-provided identifier, unique per request. Re-sending the same request_id returns the existing job instead of generating again. Also usable with the results endpoint."
  4. Changed2 schema fields changed
    • changedInput schema / properties / requestBody / properties / pose / enum
      Previous value: -[
      -  "World of Dinos",
      -  "World of Dinos",
      -  "World of Dinos"
      -]New value: +[
      +  "Idle (Front)",
      +  "Idle (Back)",
      +  "Idle (Left Facing)",
      +  "Idle (Right Facing)",
      +  "Walk (Left)",
      +  "Walk (Right)",
      +  "Walk (Towards the camera)",
      +  "Walk (Away from the camera)",
      +  "Run (Left)",
      +  "Run (Right)",
      +  "Run (Towards the camera)",
      +  "Run (Away from the camera)",
      +  "Crouching",
      +  "Crawling",
      +  "Sitting",
      +  "Defending / Blocking",
      +  "Attack Ready",
      +  "Jump Preparation",
      +  "Sleeping",
      +  "Flying",
      +  "Other"
      +]
    • changedInput schema / properties / requestBody / properties / pose / example
      Previous value: -"World of Dinos"New value: +"Idle (Front)"
  5. Changed2 schema fields changed
    • changedInput schema / properties / requestBody / properties / pose / enum
      Previous value: -[
      -  "Idle (Front)",
      -  "Idle (Back)",
      -  "Idle (Left Facing)",
      -  "Idle (Right Facing)",
      -  "Walk (Left)",
      -  "Walk (Right)",
      -  "Walk (Towards the camera)",
      -  "Walk (Away from the camera)",
      -  "Run (Left)",
      -  "Run (Right)",
      -  "Run (Towards the camera)",
      -  "Run (Away from the camera)",
      -  "Crouching",
      -  "Crawling",
      -  "Sitting",
      -  "Defending / Blocking",
      -  "Attack Ready",
      -  "Jump Preparation",
      -  "Sleeping",
      -  "Flying",
      -  "Other"
      -]New value: +[
      +  "World of Dinos",
      +  "World of Dinos",
      +  "World of Dinos"
      +]
    • changedInput schema / properties / requestBody / properties / pose / example
      Previous value: -"Idle (Front)"New value: +"World of Dinos"
  6. Changed1 schema field changed
    • addedInput schema / properties / requestBody / properties / request_id
      Added value: +{
      +  "description": "Optional client-provided identifier for this request. Use this to retrieve results later via the results endpoint.",
      +  "type": "string"
      +}
  7. Changed1 schema field changed
    • changedInput schema / properties / requestBody / properties / pose / enum
      Previous value: -[
      -  "Idle (Front)",
      -  "Idle (Back)",
      -  "Idle (Left Facing)",
      -  "Idle (Right Facing)",
      -  "Walk / Run (Left)",
      -  "Walk / Run (Right)",
      -  "Walk / Run (Towards the camera)",
      -  "Walk / Run (Away from the camera)",
      -  "Crouching",
      -  "Crawling",
      -  "Sleeping",
      -  "Flying",
      -  "Sitting",
      -  "Defending / Blocking",
      -  "Attack Ready",
      -  "Jump Preparation",
      -  "Other"
      -]New value: +[
      +  "Idle (Front)",
      +  "Idle (Back)",
      +  "Idle (Left Facing)",
      +  "Idle (Right Facing)",
      +  "Walk (Left)",
      +  "Walk (Right)",
      +  "Walk (Towards the camera)",
      +  "Walk (Away from the camera)",
      +  "Run (Left)",
      +  "Run (Right)",
      +  "Run (Towards the camera)",
      +  "Run (Away from the camera)",
      +  "Crouching",
      +  "Crawling",
      +  "Sitting",
      +  "Defending / Blocking",
      +  "Attack Ready",
      +  "Jump Preparation",
      +  "Sleeping",
      +  "Flying",
      +  "Other"
      +]
  8. Changed2 schema fields changed
    • changedInput schema / properties / requestBody / properties / pose / enum
      Previous value: -[
      -  "World of Dinos",
      -  "World of Dinos",
      -  "World of Dinos"
      -]New value: +[
      +  "Idle (Front)",
      +  "Idle (Back)",
      +  "Idle (Left Facing)",
      +  "Idle (Right Facing)",
      +  "Walk / Run (Left)",
      +  "Walk / Run (Right)",
      +  "Walk / Run (Towards the camera)",
      +  "Walk / Run (Away from the camera)",
      +  "Crouching",
      +  "Crawling",
      +  "Sleeping",
      +  "Flying",
      +  "Sitting",
      +  "Defending / Blocking",
      +  "Attack Ready",
      +  "Jump Preparation",
      +  "Other"
      +]
    • changedInput schema / properties / requestBody / properties / pose / example
      Previous value: -"World of Dinos"New value: +"Idle (Front)"
  9. Changed2 schema fields changed
    • changedInput schema / properties / requestBody / properties / pose / enum
      Previous value: -[
      -  "Idle (Front)",
      -  "Idle (Back)",
      -  "Idle (Left Facing)",
      -  "Idle (Right Facing)",
      -  "Walk / Run (Left)",
      -  "Walk / Run (Right)",
      -  "Walk / Run (Towards the camera)",
      -  "Walk / Run (Away from the camera)",
      -  "Crouching",
      -  "Crawling",
      -  "Sleeping",
      -  "Flying",
      -  "Sitting",
      -  "Defending / Blocking",
      -  "Attack Ready",
      -  "Jump Preparation",
      -  "Other"
      -]New value: +[
      +  "World of Dinos",
      +  "World of Dinos",
      +  "World of Dinos"
      +]
    • changedInput schema / properties / requestBody / properties / pose / example
      Previous value: -"Idle (Front)"New value: +"World of Dinos"
  10. Changed3 schema fields changed
    • changedInput schema / properties / requestBody / properties / pose / description
      Previous value: -"Target pose for the sprite. Common poses include: \"Idle (Front)\", \"Idle (Back)\", \"Idle (Left Facing)\", \"Idle (Right Facing)\", \"Walk / Run (Left)\", \"Walk / Run (Right)\", \"Walk / Run (Towards the camera)\", \"Walk / Run (Away from the camera)\", \"Crouching\", \"Crawling\", \"Sleeping\", \"Flying\", \"Sitting\", \"Defending / Blocking\", \"Attack Ready\", \"Jump Preparation\". You can also specify custom poses.\n"New value: +"Target pose for the sprite. Use the value \"Other\" to generate other poses not listed in the accepted values, and fill the field description accordingly."
    • addedInput schema / properties / requestBody / properties / pose / enum
      Added value: +[
      +  "Idle (Front)",
      +  "Idle (Back)",
      +  "Idle (Left Facing)",
      +  "Idle (Right Facing)",
      +  "Walk / Run (Left)",
      +  "Walk / Run (Right)",
      +  "Walk / Run (Towards the camera)",
      +  "Walk / Run (Away from the camera)",
      +  "Crouching",
      +  "Crawling",
      +  "Sleeping",
      +  "Flying",
      +  "Sitting",
      +  "Defending / Blocking",
      +  "Attack Ready",
      +  "Jump Preparation",
      +  "Other"
      +]
    • addedInput schema / properties / requestBody / properties / pose / example
      Added value: +"Idle (Front)"
  11. Added

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that this is an async job returning {id, status} requiring polling via getApiJob, describes the result array and motion_prompt field, explains credit holding/refund behavior, and states the per-result credit cost.

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 carries operational value: input format, output shape, credit mechanics, workflow placement, request_id tagging, and async polling behavior. It is front-loaded with the core purpose and has no filler.

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?

Given the high complexity, no output schema, and no annotations, this description is remarkably complete. It covers inputs, output structure, async polling, credit contract, sibling routing, and type restrictions. An agent has enough context to invoke the tool and interpret the result without external documentation.

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. The description adds cross-parameter context beyond the schema by summarizing image as URL/base64, explaining the 'Other' pose with free-text description, and tying request_id to listGenerations with type spritesheet. It does not mention augment_prompt, but the schema already fully documents that parameter.

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 opens with a specific verb and resource: 'Re-pose an existing sprite into a new target pose while preserving the character.' It also distinguishes itself from siblings by stating when to use animateSprite versus rotateSprite and explicitly restricting input to sprite image types.

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 workflow guidance: call generatePose first, then feed the result and suggested motion_prompt into animateSprite for best animation quality, and use rotateSprite instead when changing camera angle rather than pose. It also states a clear negative condition: only sprite image types, not icons or screenshots.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.