Skip to main content
Glama

Create Character

create_character
Destructive

[write, priced] Create a character (DRAFT). character_name is required and is a full name (first and last name, else ERR_CHARACTER_NAME_FULL), and so are the two accounts inside character: the storage account (character_storages_account_id or character_storages_account_uuid) and the AI account that draws the main picture (character_ai_provider + character_ai_account_uuid, the account's uuid from its provider's account list); without them it answers ERR_CHARACTER_STORAGES_ACCOUNT_REQUIRED / ERR_CHARACTER_AI_ACCOUNT_REQUIRED; character_description is the free description of the character (up to 4000 characters, saved as character_prompt); character holds any other field of the form: character_style (PHOTOREAL | REALISTIC_3D | PIXAR_3D | ANIME | MANGA | CARTOON_2D), character_purpose, character_type (FEMALE | MALE | NEUTRAL), character_language (content language value, e.g. english | turkish), character_niche / character_usp / character_format / character_money (free text, up to 100 characters each), character_bio ({facebook (up to 255 characters), instagram (150), twitter (160), tiktok (80)}: the character's profile bio per social network, free text, e.g. {"instagram": "Travel & coffee ☕", "tiktok": "daily tips"}; ERR_CHARACTER_BIO when a network or length is wrong), character_note (private note, up to 500 characters, never used in prompts), character_prompt (free description), character_appearances (the look document: age_years, height_cm, weight_kg, eye_color, body_type, hair_color, skin_tone and the look codes of character_options; age_years is a NUMBER of years (1-110, e.g. 28), never text like "young" or "twenties"; height_cm and weight_kg are numbers too), character_voice, character_outfits, character_poses, character_looks, character_locations, character_profiles, character_source ({storages_account_id, url, path}: a picture to start from), character_ai_provider + character_ai_account_uuid (+ character_ai_model, character_ai_quality) = the AI account that draws it, character_storages_account_id (or character_storages_account_uuid) + character_path = where the pictures are saved (see character_options). Next: queue_character_assets with stage MAIN. Answers character_id and character_uuid.

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": {
      "character_name": "<character_name>"
    },
    "name": "create_character"
  }
}

Input Schema

NameRequiredDescriptionDefault
characterNo
character_nameYes
character_descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the bar is lower; the description still adds real value by disclosing the draft status, the priced/write nature, the validation failure codes (ERR_CHARACTER_NAME_FULL, ERR_CHARACTER_STORAGES_ACCOUNT_REQUIRED, ERR_CHARACTER_AI_ACCOUNT_REQUIRED, ERR_CHARACTER_BIO), and that character_note is never used in prompts. It leaves open what a draft can/cannot do and why the tool is flagged destructive for a create operation.

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

Conciseness3/5

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

Purpose, required fields and the next step are front-loaded, and almost every clause carries domain information rather than filler. However, it is one dense, semi-colon-chained block with no line breaks or grouping, making it hard for an agent to scan the field inventory for the nested `character` object.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a write tool with no output schema, it states the return identifiers (character_id, character_uuid), the prerequisite lookups, and the downstream call, so an agent can execute end-to-end. The gap is lifecycle context — what a DRAFT implies and how it becomes usable — which is only gestured at via the queue_character_assets hand-off.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the only structured parameter is a free-form object, so the description carries the full documentation burden — and it does: enums for character_style and character_type, per-network bio length limits, the numeric 1-110 constraint on age_years, the account/source structure, and the 4000/500/100 character caps. The few named-only fields (character_voice, character_outfits, character_poses, character_looks) are correctly deferred to character_options.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource ("Create a character (DRAFT)") and signals the lifecycle stage via the DRAFT marker plus the explicit next step (queue_character_assets with stage MAIN), which separates it from edit_character, get_character and delete_character in the sibling list. It never names those alternatives outright, so the differentiation is implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete preconditions (a full first+last name, a storage account, and an AI provider + account uuid, with the exact error codes returned when they are missing) and a clear follow-up action. It stops short of stating when to choose edit_character over this tool or what to do if a character with the same name already exists.

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.