Skip to main content
Glama

Embers: Tabletop RPG Toolkit

Read character-creation options

vault_get_pc_creation_options
Read-onlyIdempotent

Read the legal choices for guided character creation — the same projections vault's web wizard reads. Pass ruleset (one with guided creation: the ruleset field's list; list_rulesets gives each code's label) and kind to select one list: 'class' / 'species' / 'background' / 'feat' return the option projections (the calling user's own content plus stock, each option carrying its nested choices: skillChoices, toolChoices, startingEquipmentOptions, and per applied ability/feat — proficiencyChoices, spellChoices, spellListChoices, preparedSpells, and choice whose options carry a type; an option in a choice, and a species' lineage option, may carry abilities with their own nested choices, and a Feat option carries its prerequisites and its own choice, picked in the choice map of the selection that owns it (abilityChoices for the class, speciesAbilityChoices for the species, backgroundFeatChoices for a background's feat, backgroundAbilityChoices for a background's own abilities) keyed by that rule's _id; a background option also carries skillChoices + languages, a species option carries languages; background bump modes / feat, etc.); 'feat' returns every feat (a feat picked via an ability's choice carries its own proficiency/spell sub-choices); 'constants' returns the static reference data (skill list with attributes, ability-score methods with each method's data, language options + pick count, alignments, background bump modes, max ability score, and originFeatCategory — the feat category the background's open feat slot is restricted to; filter the 'feat' list to it for the background pick). Use this BEFORE vault_build_pc so every id and pick you send is one the user is actually entitled to. Start with 'constants' and 'class', then read 'species' / 'background' / 'feat' as the build takes shape. Campaigns and Worlds: with no campaignIds or worldIds the options are stock plus the user's own content. Ask the user which campaigns and Worlds the character will join (find campaign ids with play_list_joinable_campaigns for this ruleset, World ids with imagine_list_my_worlds / imagine_search_public_worlds) and pass them on every option read and to vault_build_pc: each chosen campaign and World adds its house content (an option that came from one carries sourceLabel, naming the Worlds or campaigns it came from), the stock every chosen World hides is left out, and the chosen Worlds' extra skills are counted as the character's skills when the options are worked out. Changing the choices can change what is offered, so read the lists again after a change. A chosen campaign or World that can no longer be joined fails the call with CREATION_CONTEXT_LOST, naming it and the reason.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>"
    },
    "name": "vault_get_pc_creation_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesWhich creation list to read. 'class' / 'species' / 'background' / 'feat' return the option projections (the user's own + stock content they may pick, with each option's nested choices — skillChoices, toolChoices, startingEquipmentOptions, and per applied ability/feat: proficiencyChoices {types,count,options}, spellChoices {count,options,prepared}, spellListChoices {categories,picks[].optionsByCategory,prepared}, preparedSpells {count} (a block's `prepared: true` = its spells land always-prepared and are EXCLUDED from the preparedSpellPicks pool), abilityScoreBump {options[].lines[]:{amount,count,eligible,max}} (supply the player's pick via `vault_build_pc.abilityBumpPicks`), and `choice` {count,options} where each option carries a `type`. An option in a `choice`, and a species' lineage option, may carry `abilities` (the rules it grants at level 1, each with these same nested choices); a Feat option also carries its `prerequisites` and its own `choice`. Picks for a nested rule's `choice` go in the choice map of the selection that owns it, keyed by that rule's `_id`: `vault_build_pc.abilityChoices` under the class, `speciesAbilityChoices` under the species, `backgroundFeatChoices` under a background's feat, `backgroundAbilityChoices` under a background's own abilities. The spellChoices / spellListChoices arrays are INDEX-ALIGNED with the authored blocks — a null entry holds the position of a block that grants nothing at the starting level; skip it when rendering but count it when keying picks. A 'background' option ALSO carries `featSpellList` (when non-null, the only list its own feat offers: that feat's spellListChoicePicks `category` must be that list) and its own `skillChoices {count,options}` (a background skill-choice grant → supply picks via `vault_build_pc.backgroundSkillProficiencies`) and `languages {fixed, choose:{count,options}}`; a 'species' option carries `languages {fixed, choose}`. For a `languages.choose` grant, supply the picks via `vault_build_pc.languageChoicePicks` keyed by that rule's `_id`; `languages.fixed` apply automatically). 'feat' returns EVERY feat (the background slot uses the `originFeatCategory` feats; a feat picked via an ability's `choice` may be any) — a picked feat carries its own proficiency/spell sub-choices. Each 'feat' option carries `repeatable`; a `repeatable` feat filling the background slot keys its `vault_build_pc` picks with a `bg:` prefix. 'constants' returns the static reference data (skill list, ability-score methods and each method's data, language options, alignments, background bump modes, max ability score, and originFeatCategory — the feat category the background's open feat slot is restricted to; filter the 'feat' list to it for the background pick). A 'class' option may carry `startingGold` {count,sides,multiplier,label} (the class's starting gold dice, taken in place of its and the background's equipment; null when the class offers none). A spellChoices block may carry `addedOptions` beside its `options`: spells a rule's expanded spell list adds (a subclass's), each with `addedBy` (the adding rules' `_id`s), offered only to a build holding one of those rules. Read 'constants' plus 'class' first; read 'species'/'background'/'feat' as the build takes shape.
rulesetNoA ruleset with guided character creation. Send the same ruleset to `vault_build_pc`.
worldIdsNoimagine Worlds the new character will join, by `_id`, from imagine_list_my_worlds (the user's own and role Worlds) and imagine_search_public_worlds (public Worlds by name). At most 10 (the app answers 400 for more). Each adds its house content and extra skills, and the stock every chosen World hides is left out of the options.
campaignIdsNoCampaigns the new character will join, by `_id`, from play_list_joinable_campaigns for this ruleset, at most 10 (the app answers 400 for more). Each adds its house rules, spells, and items to the options.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / campaignIds / description
      Previous value: -"Campaigns the new character will join, by `_id`, from play_list_joinable_campaigns for this ruleset. Each adds its house rules, spells, and items to the options."New value: +"Campaigns the new character will join, by `_id`, from play_list_joinable_campaigns for this ruleset, at most 10 (the app answers 400 for more). Each adds its house rules, spells, and items to the options."
    • changedInput schema / properties / worldIds / description
      Previous value: -"imagine Worlds the new character will join, by `_id`, from imagine_list_my_worlds (the user's own and role Worlds) and imagine_search_public_worlds (public Worlds by name). Each adds its house content and extra skills, and the stock every chosen World hides is left out of the options."New value: +"imagine Worlds the new character will join, by `_id`, from imagine_list_my_worlds (the user's own and role Worlds) and imagine_search_public_worlds (public Worlds by name). At most 10 (the app answers 400 for more). Each adds its house content and extra skills, and the stock every chosen World hides is left out of the options."
  2. Changed2 schema fields changed
    • addedInput schema / properties / campaignIds
      Added value: +{
      +  "description": "Campaigns the new character will join, by `_id`, from play_list_joinable_campaigns for this ruleset. Each adds its house rules, spells, and items to the options.",
      +  "items": {
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / worldIds
      Added value: +{
      +  "description": "imagine Worlds the new character will join, by `_id`, from imagine_list_my_worlds (the user's own and role Worlds) and imagine_search_public_worlds (public Worlds by name). Each adds its house content and extra skills, and the stock every chosen World hides is left out of the options.",
      +  "items": {
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / kind / description
      Previous value: -"Which creation list to read. 'class' / 'species' / 'background' / 'feat' return the option projections (the user's own + stock content they may pick, with each option's nested choices — skillChoices, toolChoices, startingEquipmentOptions, and per applied ability/feat: proficiencyChoices {types,count,options}, spellChoices {count,options,prepared}, spellListChoices {categories,picks[].optionsByCategory,prepared}, preparedSpells {count} (a block's `prepared: true` = its spells land always-prepared and are EXCLUDED from the preparedSpellPicks pool), abilityScoreBump {options[].lines[]:{amount,count,eligible,max}} (supply the player's pick via `vault_build_pc.abilityBumpPicks`), and `choice` {count,options} where each option carries a `type`. The spellChoices / spellListChoices arrays are INDEX-ALIGNED with the authored blocks — a null entry holds the position of a block that grants nothing at the starting level; skip it when rendering but count it when keying picks. A 'background' option ALSO carries `featSpellList` (when non-null, the only list its own feat offers: that feat's spellListChoicePicks `category` must be that list) and its own `skillChoices {count,options}` (a background skill-choice grant → supply picks via `vault_build_pc.backgroundSkillProficiencies`) and `languages {fixed, choose:{count,options}}`; a 'species' option carries `languages {fixed, choose}`. For a `languages.choose` grant, supply the picks via `vault_build_pc.languageChoicePicks` keyed by that rule's `_id`; `languages.fixed` apply automatically). 'feat' returns EVERY feat (the background slot uses the `originFeatCategory` feats; a feat picked via an ability's `choice` may be any) — a picked feat carries its own proficiency/spell sub-choices. Each 'feat' option carries `repeatable`; a `repeatable` feat filling the background slot keys its `vault_build_pc` picks with a `bg:` prefix. 'constants' returns the static reference data (skill list, ability-score methods and each method's data, language options, alignments, background bump modes, max ability score, and originFeatCategory — the feat category the background's open feat slot is restricted to; filter the 'feat' list to it for the background pick). A 'class' option may carry `startingGold` {count,sides,multiplier,label} (the class's starting gold dice, taken in place of its and the background's equipment; null when the class offers none). A spellChoices block may carry `addedOptions` beside its `options`: spells a rule's expanded spell list adds (a subclass's), each with `addedBy` (the adding rules' `_id`s), offered only to a build holding one of those rules. Read 'constants' plus 'class' first; read 'species'/'background'/'feat' as the build takes shape."New value: +"Which creation list to read. 'class' / 'species' / 'background' / 'feat' return the option projections (the user's own + stock content they may pick, with each option's nested choices — skillChoices, toolChoices, startingEquipmentOptions, and per applied ability/feat: proficiencyChoices {types,count,options}, spellChoices {count,options,prepared}, spellListChoices {categories,picks[].optionsByCategory,prepared}, preparedSpells {count} (a block's `prepared: true` = its spells land always-prepared and are EXCLUDED from the preparedSpellPicks pool), abilityScoreBump {options[].lines[]:{amount,count,eligible,max}} (supply the player's pick via `vault_build_pc.abilityBumpPicks`), and `choice` {count,options} where each option carries a `type`. An option in a `choice`, and a species' lineage option, may carry `abilities` (the rules it grants at level 1, each with these same nested choices); a Feat option also carries its `prerequisites` and its own `choice`. Picks for a nested rule's `choice` go in the choice map of the selection that owns it, keyed by that rule's `_id`: `vault_build_pc.abilityChoices` under the class, `speciesAbilityChoices` under the species, `backgroundFeatChoices` under a background's feat, `backgroundAbilityChoices` under a background's own abilities. The spellChoices / spellListChoices arrays are INDEX-ALIGNED with the authored blocks — a null entry holds the position of a block that grants nothing at the starting level; skip it when rendering but count it when keying picks. A 'background' option ALSO carries `featSpellList` (when non-null, the only list its own feat offers: that feat's spellListChoicePicks `category` must be that list) and its own `skillChoices {count,options}` (a background skill-choice grant → supply picks via `vault_build_pc.backgroundSkillProficiencies`) and `languages {fixed, choose:{count,options}}`; a 'species' option carries `languages {fixed, choose}`. For a `languages.choose` grant, supply the picks via `vault_build_pc.languageChoicePicks` keyed by that rule's `_id`; `languages.fixed` apply automatically). 'feat' returns EVERY feat (the background slot uses the `originFeatCategory` feats; a feat picked via an ability's `choice` may be any) — a picked feat carries its own proficiency/spell sub-choices. Each 'feat' option carries `repeatable`; a `repeatable` feat filling the background slot keys its `vault_build_pc` picks with a `bg:` prefix. 'constants' returns the static reference data (skill list, ability-score methods and each method's data, language options, alignments, background bump modes, max ability score, and originFeatCategory — the feat category the background's open feat slot is restricted to; filter the 'feat' list to it for the background pick). A 'class' option may carry `startingGold` {count,sides,multiplier,label} (the class's starting gold dice, taken in place of its and the background's equipment; null when the class offers none). A spellChoices block may carry `addedOptions` beside its `options`: spells a rule's expanded spell list adds (a subclass's), each with `addedBy` (the adding rules' `_id`s), offered only to a build holding one of those rules. Read 'constants' plus 'class' first; read 'species'/'background'/'feat' as the build takes shape."
  4. Changed2 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Which creation list to read. 'class' / 'species' / 'background' / 'feat' return the option projections (the user's own + stock content they may pick, with each option's nested choices — skillChoices, toolChoices, startingEquipmentOptions, and per applied ability/feat: proficiencyChoices {types,count,options}, spellChoices {count,options,prepared}, spellListChoices {categories,picks[].optionsByCategory,prepared}, preparedSpells {count} (a block's `prepared: true` = its spells land always-prepared and are EXCLUDED from the preparedSpellPicks pool), abilityScoreBump {options[].lines[]:{amount,count,eligible,max}} (supply the player's pick via `vault_build_pc.abilityBumpPicks`), and `choice` {count,options} where each option carries a `type`. The spellChoices / spellListChoices arrays are INDEX-ALIGNED with the authored blocks — a null entry holds the position of a block that grants nothing at the starting level; skip it when rendering but count it when keying picks. A 'background' option ALSO carries `featSpellList` (when non-null, the only list its own feat offers: that feat's spellListChoicePicks `category` must be that list) and its own `skillChoices {count,options}` (a background skill-choice grant → supply picks via `vault_build_pc.backgroundSkillProficiencies`) and `languages {fixed, choose:{count,options}}`; a 'species' option carries `languages {fixed, choose}`. For a `languages.choose` grant, supply the picks via `vault_build_pc.languageChoicePicks` keyed by that rule's `_id`; `languages.fixed` apply automatically). 'feat' returns EVERY feat (the background slot uses the `originFeatCategory` feats; a feat picked via an ability's `choice` may be any) — a picked feat carries its own proficiency/spell sub-choices. Each 'feat' option carries `repeatable`; a `repeatable` feat filling the background slot keys its `vault_build_pc` picks with a `bg:` prefix. 'constants' returns the static reference data (skill list, ability-score methods and each method's data, language options, alignments, background bump modes, max ability score, and originFeatCategory — the feat category the background's open feat slot is restricted to; filter the 'feat' list to it for the background pick). Read 'constants' plus 'class' first; read 'species'/'background'/'feat' as the build takes shape."New value: +"Which creation list to read. 'class' / 'species' / 'background' / 'feat' return the option projections (the user's own + stock content they may pick, with each option's nested choices — skillChoices, toolChoices, startingEquipmentOptions, and per applied ability/feat: proficiencyChoices {types,count,options}, spellChoices {count,options,prepared}, spellListChoices {categories,picks[].optionsByCategory,prepared}, preparedSpells {count} (a block's `prepared: true` = its spells land always-prepared and are EXCLUDED from the preparedSpellPicks pool), abilityScoreBump {options[].lines[]:{amount,count,eligible,max}} (supply the player's pick via `vault_build_pc.abilityBumpPicks`), and `choice` {count,options} where each option carries a `type`. The spellChoices / spellListChoices arrays are INDEX-ALIGNED with the authored blocks — a null entry holds the position of a block that grants nothing at the starting level; skip it when rendering but count it when keying picks. A 'background' option ALSO carries `featSpellList` (when non-null, the only list its own feat offers: that feat's spellListChoicePicks `category` must be that list) and its own `skillChoices {count,options}` (a background skill-choice grant → supply picks via `vault_build_pc.backgroundSkillProficiencies`) and `languages {fixed, choose:{count,options}}`; a 'species' option carries `languages {fixed, choose}`. For a `languages.choose` grant, supply the picks via `vault_build_pc.languageChoicePicks` keyed by that rule's `_id`; `languages.fixed` apply automatically). 'feat' returns EVERY feat (the background slot uses the `originFeatCategory` feats; a feat picked via an ability's `choice` may be any) — a picked feat carries its own proficiency/spell sub-choices. Each 'feat' option carries `repeatable`; a `repeatable` feat filling the background slot keys its `vault_build_pc` picks with a `bg:` prefix. 'constants' returns the static reference data (skill list, ability-score methods and each method's data, language options, alignments, background bump modes, max ability score, and originFeatCategory — the feat category the background's open feat slot is restricted to; filter the 'feat' list to it for the background pick). A 'class' option may carry `startingGold` {count,sides,multiplier,label} (the class's starting gold dice, taken in place of its and the background's equipment; null when the class offers none). A spellChoices block may carry `addedOptions` beside its `options`: spells a rule's expanded spell list adds (a subclass's), each with `addedBy` (the adding rules' `_id`s), offered only to a build holding one of those rules. Read 'constants' plus 'class' first; read 'species'/'background'/'feat' as the build takes shape."
    • changedInput schema / properties / ruleset / enum
      Previous value: -[
      -  "5e24"
      -]New value: +[
      +  "5th Edition",
      +  "5e24"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / kind / description
      Previous value: -"Which creation list to read. 'class' / 'species' / 'background' / 'feat' return the option projections (the user's own + stock content they may pick, with each option's nested choices — skillChoices, toolChoices, startingEquipmentOptions, and per applied ability/feat: proficiencyChoices {types,count,options}, spellChoices {count,options,prepared}, spellListChoices {categories,picks[].optionsByCategory,prepared}, preparedSpells {count} (a block's `prepared: true` = its spells land always-prepared and are EXCLUDED from the preparedSpellPicks pool), abilityScoreBump {options[].lines[]:{amount,count,eligible,max}} (supply the player's pick via `vault_build_pc.abilityBumpPicks`), and `choice` {count,options} where each option carries a `type`. The spellChoices / spellListChoices arrays are INDEX-ALIGNED with the authored blocks — a null entry holds the position of a block that grants nothing at the starting level; skip it when rendering but count it when keying picks. A 'background' option ALSO carries its own `skillChoices {count,options}` (a background skill-choice grant → supply picks via `vault_build_pc.backgroundSkillProficiencies`) and `languages {fixed, choose:{count,options}}`; a 'species' option carries `languages {fixed, choose}`. For a `languages.choose` grant, supply the picks via `vault_build_pc.languageChoicePicks` keyed by that rule's `_id`; `languages.fixed` apply automatically). 'feat' returns EVERY feat (the background slot uses the `originFeatCategory` feats; a feat picked via an ability's `choice` may be any) — a picked feat carries its own proficiency/spell sub-choices. Each 'feat' option carries `repeatable`; a `repeatable` feat filling the background slot keys its `vault_build_pc` picks with a `bg:` prefix. 'constants' returns the static reference data (skill list, ability-score methods and each method's data, language options, alignments, background bump modes, max ability score, and originFeatCategory — the feat category the background's open feat slot is restricted to; filter the 'feat' list to it for the background pick). Read 'constants' plus 'class' first; read 'species'/'background'/'feat' as the build takes shape."New value: +"Which creation list to read. 'class' / 'species' / 'background' / 'feat' return the option projections (the user's own + stock content they may pick, with each option's nested choices — skillChoices, toolChoices, startingEquipmentOptions, and per applied ability/feat: proficiencyChoices {types,count,options}, spellChoices {count,options,prepared}, spellListChoices {categories,picks[].optionsByCategory,prepared}, preparedSpells {count} (a block's `prepared: true` = its spells land always-prepared and are EXCLUDED from the preparedSpellPicks pool), abilityScoreBump {options[].lines[]:{amount,count,eligible,max}} (supply the player's pick via `vault_build_pc.abilityBumpPicks`), and `choice` {count,options} where each option carries a `type`. The spellChoices / spellListChoices arrays are INDEX-ALIGNED with the authored blocks — a null entry holds the position of a block that grants nothing at the starting level; skip it when rendering but count it when keying picks. A 'background' option ALSO carries `featSpellList` (when non-null, the only list its own feat offers: that feat's spellListChoicePicks `category` must be that list) and its own `skillChoices {count,options}` (a background skill-choice grant → supply picks via `vault_build_pc.backgroundSkillProficiencies`) and `languages {fixed, choose:{count,options}}`; a 'species' option carries `languages {fixed, choose}`. For a `languages.choose` grant, supply the picks via `vault_build_pc.languageChoicePicks` keyed by that rule's `_id`; `languages.fixed` apply automatically). 'feat' returns EVERY feat (the background slot uses the `originFeatCategory` feats; a feat picked via an ability's `choice` may be any) — a picked feat carries its own proficiency/spell sub-choices. Each 'feat' option carries `repeatable`; a `repeatable` feat filling the background slot keys its `vault_build_pc` picks with a `bg:` prefix. 'constants' returns the static reference data (skill list, ability-score methods and each method's data, language options, alignments, background bump modes, max ability score, and originFeatCategory — the feat category the background's open feat slot is restricted to; filter the 'feat' list to it for the background pick). Read 'constants' plus 'class' first; read 'species'/'background'/'feat' as the build takes shape."
  6. Changed2 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Which 5e24 creation list to read. 'class' / 'species' / 'background' / 'feat' return the option projections (the user's own + stock content they may pick, with each option's nested choices — skillChoices, toolChoices, startingEquipmentOptions, and per applied ability/feat: proficiencyChoices {types,count,options}, spellChoices {count,options,prepared}, spellListChoices {categories,picks[].optionsByCategory,prepared}, preparedSpells {count} (a block's `prepared: true` = its spells land always-prepared and are EXCLUDED from the preparedSpellPicks pool), abilityScoreBump {options[].lines[]:{amount,count,eligible,max}} (supply the player's pick via `vault_build_pc.abilityBumpPicks`), and `choice` {count,options} where each option carries a `type`. The spellChoices / spellListChoices arrays are INDEX-ALIGNED with the authored blocks — a null entry holds the position of a block that grants nothing at level 1; skip it when rendering but count it when keying picks. A 'background' option ALSO carries its own `skillChoices {count,options}` (a background skill-choice grant → supply picks via `vault_build_pc.backgroundSkillProficiencies`) and `languages {fixed, choose:{count,options}}`; a 'species' option carries `languages {fixed, choose}`. For a `languages.choose` grant, supply the picks via `vault_build_pc.languageChoicePicks` keyed by that rule's `_id`; `languages.fixed` apply automatically). 'feat' returns EVERY feat (the background slot uses Origin-category feats; a feat picked via an ability's `choice` may be any) — a picked feat carries its own proficiency/spell sub-choices. Each 'feat' option carries `repeatable`; a `repeatable` feat filling the background slot keys its `vault_build_pc` picks with a `bg:` prefix. 'constants' returns the static reference data (skill list, ability-score methods and their arrays/point-buy costs, language options, alignments, background bump modes, max ability score, and originFeatCategory — the feat category the background's open feat slot is restricted to; filter the 'feat' list to it for the background pick). Read 'constants' plus 'class' first; read 'species'/'background'/'feat' as the build takes shape."New value: +"Which creation list to read. 'class' / 'species' / 'background' / 'feat' return the option projections (the user's own + stock content they may pick, with each option's nested choices — skillChoices, toolChoices, startingEquipmentOptions, and per applied ability/feat: proficiencyChoices {types,count,options}, spellChoices {count,options,prepared}, spellListChoices {categories,picks[].optionsByCategory,prepared}, preparedSpells {count} (a block's `prepared: true` = its spells land always-prepared and are EXCLUDED from the preparedSpellPicks pool), abilityScoreBump {options[].lines[]:{amount,count,eligible,max}} (supply the player's pick via `vault_build_pc.abilityBumpPicks`), and `choice` {count,options} where each option carries a `type`. The spellChoices / spellListChoices arrays are INDEX-ALIGNED with the authored blocks — a null entry holds the position of a block that grants nothing at the starting level; skip it when rendering but count it when keying picks. A 'background' option ALSO carries its own `skillChoices {count,options}` (a background skill-choice grant → supply picks via `vault_build_pc.backgroundSkillProficiencies`) and `languages {fixed, choose:{count,options}}`; a 'species' option carries `languages {fixed, choose}`. For a `languages.choose` grant, supply the picks via `vault_build_pc.languageChoicePicks` keyed by that rule's `_id`; `languages.fixed` apply automatically). 'feat' returns EVERY feat (the background slot uses the `originFeatCategory` feats; a feat picked via an ability's `choice` may be any) — a picked feat carries its own proficiency/spell sub-choices. Each 'feat' option carries `repeatable`; a `repeatable` feat filling the background slot keys its `vault_build_pc` picks with a `bg:` prefix. 'constants' returns the static reference data (skill list, ability-score methods and each method's data, language options, alignments, background bump modes, max ability score, and originFeatCategory — the feat category the background's open feat slot is restricted to; filter the 'feat' list to it for the background pick). Read 'constants' plus 'class' first; read 'species'/'background'/'feat' as the build takes shape."
    • addedInput schema / properties / ruleset
      Added value: +{
      +  "description": "A ruleset with guided character creation. Send the same ruleset to `vault_build_pc`.",
      +  "enum": [
      +    "5e24"
      +  ],
      +  "type": "string"
      +}
  7. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already establish this is a safe, idempotent, non-open-world read, and the description goes well past them: chosen Worlds hide stock content and add extra skills, sourced options carry sourceLabel, stale campaign/World context fails with CREATION_CONTEXT_LOST naming the cause, and changing picks changes what is offered. These are non-obvious behavioral effects an agent could not infer from the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one enormous paragraph of stacked parentheticals enumerating nested return fields (skillChoices, spellListChoices, preparedSpells, addedOptions, etc.) that the output schema and the `kind` parameter description already cover. Front-loading is good, but the middle is nearly unparseable and much of it is redundant with structured fields.

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?

Given the complexity — five option kinds, campaign/World scoping, and an intricate pick-keying scheme — the definition leaves nothing an agent needs unanswered, including the failure mode. It overshoots by re-documenting return structures that an output schema already defines, but it is not incomplete.

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% and the schema text is itself extremely detailed, so the description largely restates parameter meaning rather than adding to it. The genuinely additive pieces are minor — that `ruleset` must be one with guided creation (per list_rulesets) and that the same ruleset must be passed to vault_build_pc. Baseline 3 for high schema coverage.

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 opening sentence gives a specific verb and resource — 'Read the legal choices for guided character creation' — and immediately scopes it ('the same projections vault's web wizard reads'). It also distinguishes the tool from vault_build_pc (this is the read that precedes the write) and from list_rulesets (which supplies labels rather than 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?

Explicit ordering guidance is given: 'Use this BEFORE vault_build_pc', 'Start with constants and class, then read species/background/feat as the build takes shape', and re-read after any choice change. It also names the prerequisite discovery tools (list_rulesets, play_list_joinable_campaigns, imagine_list_my_worlds, imagine_search_public_worlds) and tells the agent to ask the user about campaigns/Worlds first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources