TTRPG campaign management server with dice rolling and session/lore note management
Single tool 'roll_dice' has a well-structured definition with good description, clear input schema using Zod validation, and documented output schema. Tool naming is verb-first and descriptive. Parameters have types and descriptions. However, the server lacks error handling guidance (what happens on invalid notation?), and output schema lacks description/documentation in the source code comments. The parameter descriptions include examples embedded in the description text rather than using enum/format constraints where applicable. Overall solid but with room for error handling maturity.
Roll dice using standard notation. Supports: NdM+K (basic), khN/klN (keep highest/lowest), dhN/dlN (drop highest/lowest), ! (exploding), r<N/r>N (reroll), nested expressions like (2d6+1)d4, and // comments. Use advantage: "adv" or "dis" for D&D 5e style advantage/disadvantage on d20 rolls.
Output schema defined in Zod but lacks descriptive documentation in code. LLMs cannot see field meanings (what does 'breakdown' contain? Is 'detail' free text or structured?).
No error handling guidance. What happens if user passes invalid notation like '2d20kh5' (keep high 5 when rolling 2d20)? Should the tool reject it, silently clamp, or return an error message? LLM has no recovery path.
Parameter descriptions embed example values ('e.g., "2d20kh1+5"'). Best practice is to use formal constraints (regex, enum) rather than examples, which LLMs may treat as the only valid options.
No documentation of what constitutes valid/invalid dice notation. Format, bounds, and operators are mentioned casually in description but not formally validated with clear error messages.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 0 | 2025-06-18+ | v2 |
| 2026-03-09 | F | 47 | - | v1 |