Skip to main content
Glama

Create a character sheet

create_character_sheet
Idempotent

Make a character sheet for one of your series: 4-6 AI images (default 5: front portrait, full body, side, expressions) of ONE fictional character, from a text description. CHARGES credits: 23 credits for 5 images of a person, 11 for an animal or mascot. ALWAYS call get_character_sheet first and tell the human the price: the human, not the agent, decides to spend. This tool refuses unless confirm is true, expectedCredits equals the price computed now (a changed price answers 409 PRICE_CHANGED and charges nothing) and idempotencyKey is set; StoryShort has no daily spending cap per key, so these are the guard. Credits are taken when it starts and returned in full if no sheet comes back. If a non-primary view 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). Characters are fictional adults (or animals / mascots), AI-generated: no real or famous people, no children or anyone who looks under 18, no sexual content, no logos or protected characters (refused with CONTENT_POLICY, nothing charged). Everything made here is AI-generated and labelled as such. A series can hold 3 sheets in total; the first sheet is chosen automatically. A series made with create_series has no saved character description: pass description. Requires the "video:create" scope.

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>",
      "confirm": "<confirm>",
      "expectedCredits": "<expectedCredits>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "create_character_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true: making a sheet spends credits, and the human has seen the price.
seriesIdYesA series id from 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.
idempotencyKeyYesRequired. One new unique key per purchase; a repeat with the same key returns the first answer (replayed: true) and charges nothing.
expectedCreditsYesThe price the human saw (get_character_sheet quotes for this kind and image count). Must equal the price computed now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say it is not read-only, is idempotent and is open-world; the description supplies the economically critical behavior an agent cannot infer: 23 vs 11 credit pricing, charge-on-start with full refund on failure, partial sheets with creditsCharged and missingViews, the 409 PRICE_CHANGED path that charges nothing, the absence of a daily spend cap, content-policy refusals with nothing charged, and expected latency. This is exactly the extra context the annotations do not carry.

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 correctly: action, price and the get_character_sheet-first rule appear in the first two sentences. It is a dense single block of semicolon-chained clauses with some redundancy (the refund promise is stated twice, once generally and once for the slow-image-model case), so structure costs it a point despite little true 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?

With no output schema, the description still tells the agent what comes back (the images themselves, partial: true, missingViews, creditsCharged, replayed: true) and what failures look like (409 PRICE_CHANGED, CONTENT_POLICY, slow-model failure with refund). For a mutation tool that spends money, all the decision-relevant behavior is present.

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, but the description adds real meaning beyond the field text: expectedCredits is tied to the live quote and to the 409 outcome, idempotencyKey is framed as the anti-double-charge guard in place of a spending cap, imageCount's default of 5 is restated alongside the paid-per-view refund rule, and description's omission behavior versus a saved series description is spelled out.

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?

Opens with a specific verb and resource: 'Make a character sheet for one of your series: 4-6 AI images ... of ONE fictional character, from a text description.' The count, the view list (front portrait, full body, side, expressions) and the singular-character constraint make it unmistakably distinct from get_character_sheet, create_character_episode and create_video.

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?

Gives an explicit prerequisite ('ALWAYS call get_character_sheet first and tell the human the price'), states who decides ('the human, not the agent, decides to spend'), and covers a conditional branch ('A series made with create_series has no saved character description: pass description'). Nothing about when to use this versus the read-only sibling is left to inference.

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.

Resources