Skip to main content
Glama

create_character

Generate RPG characters for tabletop games with customizable stats, classes, races, and types. Only a name is required—all other attributes use sensible defaults.

Instructions

Create a new character. Only name is required - everything else has sensible defaults.

Character types:

  • pc: Player character (default)

  • npc: Non-player character (ally or neutral)

  • enemy: Hostile creature

  • neutral: Non-hostile, non-ally

Class and race can be ANY string - use standard D&D classes/races or create custom ones. Stats can be any positive integer (not limited to 3-18).

Example (minimal - just name): { "name": "Mysterious Stranger" }

Example (full): { "name": "Valeros", "class": "Fighter", "race": "Human", "hp": 20, "maxHp": 20, "ac": 18, "level": 1, "stats": { "str": 16, "dex": 14, "con": 14, "int": 10, "wis": 12, "cha": 10 }, "characterType": "pc" }

Example (custom class/race): { "name": "Whiskers", "class": "Chronomancer", "race": "Mousefolk", "stats": { "str": 6, "dex": 18, "con": 10, "int": 16, "wis": 14, "cha": 12 } }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCharacter name (required)
classNoCharacter class - any string allowed (Fighter, Wizard, Chronomancer, Merchant...)Adventurer
raceNoCharacter race - any string allowed (Human, Elf, Mousefolk, Illithid...)Human
backgroundNoFolk Hero
alignmentNo
statsNo
hpNo
maxHpNo
acNo
levelNo
characterTypeNopc
factionIdNo
behaviorNo
characterClassNo
knownSpellsNo
preparedSpellsNo
resistancesNo
vulnerabilitiesNo
immunitiesNo
provisionEquipmentNoAuto-grant class-appropriate starting equipment and spells. Set to false for custom/improvised characters.
customEquipmentNoOverride default starting equipment with these items (still requires provisionEquipment: true)
startingGoldNoOverride default starting gold amount
sessionIdNo
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool creates a new character (a write operation) and provides examples of behavior, but doesn't mention permissions, rate limits, side effects, or what happens on failure. The examples help, but key behavioral traits like persistence and error handling are missing.

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?

The description is appropriately sized for a complex tool with 23 parameters. It's front-loaded with the core purpose and defaults, followed by organized sections for character types and examples. Every sentence earns its place by providing essential guidance, though the examples are lengthy but necessary for clarity.

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?

Given the tool's complexity (23 parameters, nested objects, no output schema, and no annotations), the description does a good job of providing context. It explains the creation process, parameter flexibility, and includes examples. However, it doesn't cover return values or error cases, which would be needed for full completeness given the lack of output schema.

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?

With only 26% schema description coverage, the description compensates extensively by explaining parameter semantics beyond the schema. It clarifies that 'class and race can be ANY string', 'stats can be any positive integer', provides character type definitions, and gives three detailed examples showing minimal and full usage. This adds significant value over the sparse schema descriptions.

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 description explicitly states the tool's purpose as 'Create a new character' with the verb 'Create' and resource 'character'. It distinguishes from siblings like 'batch_create_characters', 'update_character', and 'delete_character' by focusing on single character creation with detailed customization options.

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?

The description provides clear context for usage by stating 'Only name is required - everything else has sensible defaults' and explaining character types with defaults. It doesn't explicitly mention when not to use this tool versus alternatives like 'batch_create_characters' or 'spawn_equipped_character', but the detailed parameter guidance implies this is for manual character creation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mnehmos/rpg-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server