FilmLab

Create Character

lab_create_character

Create a character sheet for a human, animal or creature in the cast register. The backend derives an English prompt_prefix_en from the fields you give — that prefix is what later describes this character in every image, so the richer the description, the more stable the identity. This is step 1 of 2: a fresh sheet has NO reference image and is therefore not yet usable as character_refs. Run lab_generate_character_reference on the returned id to finish it. Free — it writes a row, it burns no credits.

Input Schema

TableJSON Schema

Name	Required	Description
`age`	No	Age in years, as a number
`eyes`	No	Eye colour and expression
`hair`	No	Hair colour, length, cut
`name`	Yes	Character name, e.g. 'Maren' — the only required field
`skin`	No	Skin tone and texture
`build`	No	Body build and posture
`gender`	No	e.g. 'female', 'male', 'non-binary'
`gattung`	No	Character kind: human, animal or creature. Omitted or empty means mensch. For tier/kreatur, begin the description with the species and its distinctive features.
`clothing`	No	Default costume the character is seen in
`demeanor`	No	How the character moves and behaves, in prose
`project_id`	No	Bind the sheet to this project (from lab_list_projects) — positive integer as string. PASS THIS whenever the character belongs to a project. Without it the sheet stays an orphan: lab_cast_gaps will not count it as created, and image generation will not find it as a char_ref.
`project_name`	No	Free-text project label shown in listings (does NOT bind the sheet — that is project_id)
`facial_features`	No	Face shape, nose, mouth, jaw — what makes this face recognisable
`distinctive_features`	No	Scars, tattoos, glasses, anything that must appear in every image

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed2 schema fields changedOct 11, 2026

changedInput schema / properties / demeanor / description

Previous value: -"How the person carries themselves, in prose"New value: +"How the character moves and behaves, in prose"

addedInput schema / properties / gattung

Added value: +{
+  "description": "Character kind: human, animal or creature. Omitted or empty means mensch. For tier/kreatur, begin the description with the species and its distinctive features.",
+  "enum": [
+    "mensch",
+    "tier",
+    "kreatur",
+    ""
+  ],
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.9/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 readOnlyHint=false and destructiveHint=false. It discloses a real side effect (the backend derives an English prompt_prefix_en that drives later image identity), the cost profile ('Free ... burns no credits'), and an important state limitation (a fresh sheet has no reference image and is not yet usable as character_refs).

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?

Four sentences, each carrying distinct information (what it creates, the derived prefix, the 2-step workflow, the cost/credit facts), front-loaded with the core purpose. No restatement of the title or 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?

For a 14-parameter creation tool with no output schema and only a readOnly/destructive annotation pair, the description covers purpose, cost, side effects, workflow ordering, project binding, and even a lightweight statement of the return value (the id). Nothing an agent needs to call this correctly is missing.

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 schema already documents all 14 fields, setting a baseline of 3. The description still adds cross-parameter guidance the schema lacks: 'the richer the description, the more stable the identity' tells the agent the descriptive fields are load-bearing rather than cosmetic.

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 ('Create a character sheet ... in the cast register') and explicitly positions itself as 'step 1 of 2', which separates it cleanly from lab_generate_character_reference, lab_create_location and lab_get_character in the sibling list.

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 explicit sequencing ('Run lab_generate_character_reference on the returned id to finish it') and a conditional instruction with a named consequence ('PASS THIS whenever the character belongs to a project. Without it the sheet stays an orphan: lab_cast_gaps will not count it as created'). An agent knows both when to call it and what to call next.

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

All FilmLab tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?