Skip to main content
Glama
rbilleci

bsh-mcp

by rbilleci

character_advance

Advance a character by one level: add hit points, attribute increases, and Gift; upgrade Doom die at level 10. Requires enough Stories and no active combat.

Instructions

Advance one player character by exactly one level.

Call this when the table levels a character up. The tool refuses unless the character has collected Stories equal to their current level, so check eligibility with character_sheet or session_close first. Advancing two levels needs two calls, each with that level's own choices.

The tool adds the level's hit point, applies the player's chosen attribute increases and Gift, and upgrades the Doom die to d8 at level 10. It rejects a choice that does not match the level's benefits and writes nothing. It also refuses while combat is active: advance between encounters, not mid-fight.

attribute_increases: the attributes the player raises this level, from STR, DEX, CON, INT, WIS, CHA. Levels 2 and 6 raise one; levels 4 and 8 raise two distinct attributes. Each raised attribute must sit below 18. Other levels raise none. gift_id: at levels 3, 5, 7, and 9, one Gift id from rules/gifts.json the character does not already hold. Leave it empty at other levels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gift_idNo
character_idYes
attribute_increasesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so thoroughly. It discloses exact effects (adds hit points, applies attribute increases and Gift, upgrades Doom die at level 10) and failure behavior ('rejects a choice... and writes nothing'), plus the Stories and combat eligibility gates.

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?

The description is front-loaded with the core action, then proceeds logically through usage conditions, effects, and parameter contracts. Each sentence adds operational value, and the parameter sections are organized so the agent can easily map rules to inputs.

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

Completeness5/5

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

For a state-changing tool with no annotations and no output schema, this description provides prerequisites, level-specific rules, failure behavior, and usage constraints. An agent has enough information to decide when to call it and how to populate every parameter correctly.

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%, but the description compensates fully: attribute_increases lists allowed attributes, per-level counts, distinctness, and the below-18 cap, while gift_id specifies levels, source file, not-already-held condition, and empty default. character_id is self-evident from its name and required status.

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 opens with 'Advance one player character by exactly one level,' which names a specific verb, a clear resource, and an exact scope. It also states level-specific side effects, making it easy to distinguish from read-only sibling tools like character_sheet or character_options.

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?

It explicitly says 'Call this when the table levels a character up' and tells the agent to check eligibility with character_sheet or session_close first. It also covers when not to call it by saying the tool refuses during active combat, and it clarifies that advancing two levels requires two calls.

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