Skip to main content
Glama

create_character

Generate a complete D&D 5e character sheet with auto-populated stats, equipment, and abilities based on class, race, and background selections.

Instructions

Create a new player character.

When a rulebook is loaded, auto-populates the character with saving throws, proficiencies, starting equipment, features, HP, spell slots, and more from the class, race, and background definitions. Requires a rulebook to be loaded (use load_rulebook source="srd" first).

Without a rulebook, returns an error message asking to load one first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCharacter name
character_classYesPrimary character class
class_levelYesPrimary class level
raceYesCharacter race
player_nameNoThe name of the player in control of this character
descriptionNoA brief description of the character's appearance and demeanor.
bioNoThe character's backstory, personality, and motivations.
backgroundNoCharacter background
alignmentNoCharacter alignment
subclassNoPrimary class subclass name (required if level >= subclass level)
subraceNoSubrace name (e.g., 'Hill Dwarf')
additional_classesNoJSON list for multiclass: [{"name": "Wizard", "level": 3, "subclass": "Evocation"}]
ability_methodNoAbility score method: 'manual' (default), 'standard_array', or 'point_buy'manual
ability_assignmentsNoJSON dict for standard_array/point_buy: {"strength": 15, "dexterity": 14, ...}
strengthNoStrength score (manual mode)
dexterityNoDexterity score (manual mode)
constitutionNoConstitution score (manual mode)
intelligenceNoIntelligence score (manual mode)
wisdomNoWisdom score (manual mode)
charismaNoCharisma score (manual mode)
Behavior4/5

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

With no annotations provided, the description carries full burden and does well. It describes the auto-population behavior (saving throws, proficiencies, etc.), prerequisite requirement (rulebook must be loaded), and error behavior (returns error message if no rulebook). However, it doesn't mention mutation effects, permissions, or rate limits.

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?

Three well-structured sentences with zero waste. First states core purpose, second explains auto-population behavior and prerequisite, third describes error case. Every sentence adds essential information.

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 creation tool with no annotations and no output schema, the description provides good context about behavior, prerequisites, and error handling. However, it doesn't describe what the tool returns upon success (character object, ID, confirmation) which would be helpful given no output schema exists.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all 20 parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema, but it does provide context about auto-population from rulebook definitions which helps understand how parameters relate to system behavior.

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 clearly states the tool creates a new player character with specific auto-population behavior when a rulebook is loaded. It distinguishes from siblings by focusing on character creation rather than modification or retrieval operations like update_character or get_character.

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?

Explicitly states when to use this tool: 'When a rulebook is loaded' and provides a clear prerequisite: 'Requires a rulebook to be loaded (use load_rulebook source="srd" first).' Also specifies what happens without a rulebook: 'Without a rulebook, returns an error message asking to load one first.'

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/Polloinfilzato/dm20-protocol'

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