Skip to main content
Glama
Sign In

Seliee

by si.seliee.mcp
OverviewDiscussionsAdmin

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 2000 characters, saved as character_prompt); character holds any other field of the form: character_style (PHOTOREAL | REALISTIC_3D | PIXAR_3D | ANIME | 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_prompt (free description), character_appearances (the look document: height_cm, weight_kg, eye_color, body_type, hair_color, skin_tone and the look codes of character_options), 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.

Input Schema

NameRequiredDescriptionDefault
characterNo
character_nameYes
character_descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / character_description
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Character Description"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare write, destructive, non-idempotent behavior, so the description does not need to restate safety basics. It adds useful context beyond annotations: "priced", DRAFT state, required storage/AI accounts, specific error codes, and returned character_id/character_uuid.

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?

The essential requirement is front-loaded, but the description becomes a dense semicolon-separated run-on. It repeats the AI account and storage account requirements in multiple places, which weakens conciseness even though most content is useful.

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 complex, priced create operation with no output schema and 0% schema coverage, the description covers required inputs, nested character fields, error outcomes, returned IDs, and the next workflow step. It leaves some lifecycle context unexplained, such as what DRAFT means operationally and how publishing works.

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%, so the description carries the full burden and does so thoroughly. It defines character_name as a full name, character_description's 2000-character limit and mapping to character_prompt, required storage and AI account fields inside character, enum values, and the many optional character fields.

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?

States a specific verb and resource: "Create a character (DRAFT)". The DRAFT qualifier and the explicit next step distinguish it from downstream asset generation, but it does not explicitly differentiate itself from siblings such as edit_character or create_character_image.

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 clear context for when to use it: create a character draft, then call queue_character_assets with stage MAIN. It also says to see character_options for storage path details. However, it does not name exclusions or alternatives such as edit_character for updating an existing character.

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

All Seliee toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources