Skip to main content
Glama

level_up_character

Increase a character's level in D&D 5e campaigns, handling HP calculation, class features, spell slots, ability score improvements, and multiclassing automatically.

Instructions

Level up a character by one level.

Increments level, calculates HP increase, adds class features, updates spell slots for casters, handles ASI at appropriate levels, and manages subclass selection. Requires a rulebook to be loaded.

Multiclass: if class_name is a class the character doesn't have yet, this acts as a multiclass dip — adding that class at level 1.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
name_or_idYesCharacter name, ID, or player name
class_nameNoWhich class to level up (for multiclass characters). If omitted, levels up primary class.
hp_methodNoHP increase method: 'average' (default, PHB standard) or 'roll'average
asi_choicesNoJSON dict for ASI: {"strength": 2} or {"strength": 1, "dexterity": 1}
subclassNoSubclass to select (at subclass level, typically 3)
new_spellsNoJSON list of new spells learned: ["fireball", "counterspell"]
player_idNoPlayer ID for permission check (omit for single-player DM mode)
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: it increments level, calculates HP, adds features, updates spell slots, handles ASI, manages subclass selection, and supports multiclassing. However, it lacks details on permissions (player_id hint), error handling, or what the tool returns, leaving gaps for a mutation tool.

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 and front-loaded, starting with the core action. Sentences earn their place by explaining multiclass behavior and prerequisites, but could be slightly more structured (e.g., bullet points for clarity). No wasted words, but minor room for improvement in organization.

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

Completeness3/5

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

Given the complexity (7 parameters, mutation tool) and no annotations or output schema, the description is moderately complete. It covers the main actions and multiclass logic, but lacks details on return values, error cases, or interaction with other tools (e.g., 'update_character'). Adequate for basic understanding but with clear gaps for full agent guidance.

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 parameters thoroughly. The description adds minimal semantics beyond the schema, mentioning multiclass behavior for 'class_name' and rulebook requirement, but does not provide additional context for parameters like 'asi_choices' or 'new_spells'. Baseline 3 is appropriate as the schema does the heavy lifting.

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 specific action ('Level up a character by one level') and resource ('character'), distinguishing it from siblings like 'create_character' or 'update_character'. It elaborates on what the level-up entails (HP increase, class features, etc.), making the purpose unambiguous.

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 when to use this tool: for leveling up characters, with a rulebook loaded. It distinguishes between single-class and multiclass scenarios, but does not explicitly state when not to use it or name alternatives among siblings (e.g., 'update_character' might be a related tool).

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