Skip to main content
Glama

Create a character sheet

autoshort_create_character_sheet
Idempotent

Create a 4-6 image character sheet for one fictional person, animal, or mascot from a text description, producing consistent views for a series.

Instructions

Make a character sheet for one of your series: 4-6 AI images (default 5: front portrait, full body, side, two expressions) of ONE fictional character, from a text description. Price: 21 credits for 5 images of a person, 10 for an animal or mascot; call autoshort_get_character_sheet first and tell the user. Credits are taken when it starts and returned in full if no sheet comes back. If a non-primary view (full body, side, an expression) could not be made in time, the sheet still comes back with the images that exist (the answer says partial: true and lists missingViews) and only those images are charged: the difference is returned and creditsCharged shows what was kept. For a person the face is carried from the front portrait into the other views; the outfit follows the description and can drift a little. For an animal or mascot the views share one description and seed, so they look alike but are not guaranteed to be identical. Usually under a minute; the answer already contains the images (a slow image model fails the call and returns the credits). Not accepted (CONTENT_POLICY, nothing charged): real or famous people, children or anyone who looks under 18, sexual content, logos or protected characters. Characters must be fictional and clearly adult (or an animal / mascot). A series can hold 3 sheets in total; the first sheet is chosen automatically. Pass idempotencyKey so a retry never charges twice.

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": {
      "seriesId": "<seriesId>"
    },
    "name": "autoshort_create_character_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesIdYesA series id from autoshort_list_series.
imageCountNoImages in the sheet (default 5).
descriptionNoThe character's look: age band, hair, outfit, colours. Omit to use the series' saved character description.
subjectKindNoPERSON (fictional adult, default), ANIMAL (pet) or MASCOT.
idempotencyKeyNoRetry-safe: a repeat with the same key returns the first answer (replayed: true) and charges nothing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations, which only declare readOnly=false/idempotent=true/destructive=false. The description discloses the credit economics (21 credits for a person, 10 for animal/mascot, charged at start, refunded in full on failure), partial-success semantics (partial: true, missingViews, only present images charged, creditsCharged), timing, and face/outfit consistency limits.

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?

Purpose and price are front-loaded in the first two sentences, and nearly every clause carries actionable information. It is long and some sentences are dense run-ons, and the closing idempotencyKey sentence largely restates the schema's own description of that field.

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?

There is no output schema, and the description compensates by describing the return shape directly (images in the answer, partial/missingViews/creditsCharged/replayed flags). Pricing, failure modes, content policy, and the series cap are all covered, which is complete for a paid generation tool with one required parameter.

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 the baseline is 3; the description still adds value by tying subjectKind to price tiers and view semantics (person face carried from the portrait vs. animal/mascot sharing one description and seed), and by reinforcing that idempotencyKey prevents double charging on retry. It does not add format detail for seriesId or imageCount beyond the schema.

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 first sentence gives a specific verb and artifact ("Make a character sheet") plus scope: 4-6 AI images of ONE fictional character from a text description, with the default view set enumerated. It also names the sibling precheck (autoshort_get_character_sheet), so the agent can separate this create call from the read call without opening either schema.

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?

Explicit prerequisites ("call autoshort_get_character_sheet first and tell the user" about price), explicit exclusions ("Not accepted (CONTENT_POLICY, nothing charged): real or famous people, children..."), and an explicit capacity constraint ("A series can hold 3 sheets in total; the first sheet is chosen automatically"). Both when-to-use and when-not-to-use are stated.

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