Skip to main content
Glama

generate_character_set

Generate consistent character images across multiple poses and expressions for turnarounds, expression sheets, mascots, and sprite sheets.

Instructions

Generate consistent character images across multiple poses and expressions for character series, mascots, or visual narratives.

Use this when:

  • Creating character turnarounds (front, side, back views)

  • Generating expression sheets for the same character

  • Building consistent mascots or characters across multiple images

  • Creating sprite sheets for games or animations

NOT for:

  • Single character image without multiple poses (use generate_image instead)

  • Editing existing character images (use edit_image instead)

  • Style transfer between images (use style_transfer instead)

Chain with: If user requests specific pixel dimensions for character images, chain with resize_image after generation.

Example: "generate_character_set characterDescription='friendly robot mascot with blue eyes' poses=['front', 'waving', 'thinking'] style='cartoon'"

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "characterDescription": "<characterDescription>",
      "style": "<style>",
      "outputFormat": "<outputFormat>",
      "quality": "<quality>",
      "aspectRatio": "<aspectRatio>",
      "size": "<size>",
      "previewMode": "<previewMode>",
      "outputMode": "<outputMode>"
    },
    "name": "generate_character_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYes2k
posesNo
styleYescartoon
qualityYes
outputModeYesindividual
aspectRatioYes1:1
expressionsNo
previewModeYes
outputFormatYespng
referenceImageNo
characterDescriptionYes
outputFilenamePrefixNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.2

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that output is a multi-image set and that sprite-sheet mode exists, and it gives a chaining rule. It says nothing about cost/time of generating up to ~16 images, how referenceImage affects consistency, what happens if poses/expressions are omitted, or whether previewMode changes the response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded opening sentence followed by scannable when/not-for/chain sections; nearly every line carries routing value. The trailing example line is somewhat redundant with the when-to-use list and its quoting format is awkward, but overall it is tight for the amount of routing information conveyed.

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?

Excellent on purpose and sibling routing, which is the hardest part for a 14-sibling namespace. But for a 12-parameter, 8-required tool with no annotations and no output schema, it leaves the behavior of half the parameters (reference images, naming, preview) and the shape of the returned set undescribed.

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 description coverage is 0% across 12 parameters, so the description must compensate and largely does not. Its example illustrates only characterDescription, poses, and style; referenceImage, outputFilenamePrefix, previewMode, quality, outputMode, aspectRatio, and size get no explanation beyond self-descriptive enum values.

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?

States a specific verb and resource ('Generate consistent character images across multiple poses and expressions') plus the target artifact classes (character series, mascots, visual narratives). It is immediately distinguishable from generate_image, edit_image, and style_transfer, which it names explicitly.

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?

Provides an explicit 'Use this when' list (turnarounds, expression sheets, mascots, sprite sheets) and a 'NOT for' list that routes three named alternatives. It also specifies a chaining rule with resize_image for pixel-dimension requests, so both tool selection and sequencing are covered.

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