Skip to main content
Glama

update_character

Modify character attributes, ability scores, conditions, proficiencies, languages, and features in Dungeons & Dragons campaigns to reflect gameplay changes and progression.

Instructions

Update a character's properties.

Supports scalar field updates, ability score changes, and list add/remove operations for conditions, proficiencies, languages, and features. List parameters accept JSON arrays (e.g. '["poisoned","prone"]') or comma-separated strings (e.g. 'poisoned,prone').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
name_or_idYesCharacter name, ID, or player name.
nameNoNew character name. If you change this, you must use the character's ID to identify them.
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
hit_points_currentNoCurrent hit points
hit_points_maxNoMaximum hit points
temporary_hit_pointsNoTemporary hit points
armor_classNoArmor class
experience_pointsNoExperience points
speedNoMovement speed in feet
character_levelNoSet the primary class level directly (e.g. to downgrade to level 1). Recalculates proficiency bonus automatically.
hit_dice_remainingNoRemaining hit dice, e.g. '1d8' or '3d10'. Use after a level change or manual rest.
inspirationNoInspiration status
notesNoAdditional notes about the character
strengthNoStrength score
dexterityNoDexterity score
constitutionNoConstitution score
intelligenceNoIntelligence score
wisdomNoWisdom score
charismaNoCharisma score
add_conditionsNoJSON list of conditions to add, e.g. '["poisoned","prone"]'
remove_conditionsNoJSON list of conditions to remove
add_skill_proficienciesNoJSON list of skill proficiencies to add
remove_skill_proficienciesNoJSON list of skill proficiencies to remove
add_tool_proficienciesNoJSON list of tool proficiencies to add
remove_tool_proficienciesNoJSON list of tool proficiencies to remove
add_languagesNoJSON list of languages to add
remove_languagesNoJSON list of languages to remove
add_saving_throw_proficienciesNoJSON list of saving throw proficiencies to add
remove_saving_throw_proficienciesNoJSON list of saving throw proficiencies to remove
add_features_and_traitsNoJSON list of features/traits to add
remove_features_and_traitsNoJSON list of features/traits to remove
player_idNoPlayer ID for permission check (omit for single-player DM mode)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the types of operations supported (scalar updates, ability score changes, list add/remove) and format details for list parameters, but lacks critical information: whether this is a destructive mutation, what permissions are needed (especially given the 'player_id' parameter), what happens on partial updates, error conditions, or response format. For a complex mutation tool with 36 parameters, this is inadequate.

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 efficiently structured with three sentences: a purpose statement, a scope overview, and format details for list parameters. Each sentence adds value without redundancy. It could be slightly more front-loaded by mentioning the key identifier parameter first, but overall it's appropriately concise for a tool with many parameters.

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

Completeness2/5

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

Given the tool's complexity (36 parameters, mutation operation, no annotations, no output schema), the description is insufficient. It should explain more about the mutation behavior: whether updates are partial or complete, what validation occurs, how errors are handled, what the response contains, and permission requirements. The format details for list parameters are helpful but don't compensate for the missing behavioral context needed for safe invocation.

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 some value by grouping parameters into categories (scalar fields, ability scores, list operations) and providing format examples for list parameters. However, it doesn't explain parameter interactions (e.g., that changing 'name' requires using ID in 'name_or_id') or semantic constraints beyond what's in individual parameter descriptions.

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?

The description clearly states the tool's purpose: 'Update a character's properties' with specific categories of updates (scalar fields, ability scores, list operations). It distinguishes from sibling tools like 'create_character' or 'delete_character' by focusing on modification rather than creation or deletion. However, it doesn't explicitly differentiate from 'bulk_update_characters' or 'level_up_character' which are more specific variants.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose 'update_character' over 'bulk_update_characters' for multiple characters, or when to use 'level_up_character' for level-specific updates versus the general 'character_level' parameter here. There's also no mention of prerequisites like character existence or permission requirements.

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