Skip to main content
Glama

get_character

Read-only

Look up a live World of Warcraft character from Blizzard's armory: profile summary (class, spec, level, item level, guild, faction) plus the sections you ask for — gear, talents, stats, M+, raid and dungeon progress, professions, PvP, achievements, collections, and more. Defaults to equipment, talents, stats, mythic_plus. Talents return only the active spec's active loadout: hero tree, the importable talent_loadout_code (pass it to decode_build), and each talent as {node_id, talent_id, name, rank}; set include_inactive_loadouts for every other saved loadout's code. Equipment is compact: equipped item level, then per item slot, name, item level, track (name_description), stats, gems, enchants, spell/proc text, set and bonus_list; set bonuses sit once in equipped_item_sets. mythic_plus returns the current season's rating and the best run per dungeon. raids and dungeons cover the current expansion only, newest release first and Mythic → Raid Finder; use raid_expansions / dungeon_expansions for others. achievements returns a summary (total points, completed count, recent completions, per-category progress); use achievement_category (paged with achievements_limit / achievements_offset) to list completions in one category, or achievement_ids to check specific achievements with criteria progress. achievement_statistics lists its categories; use statistics_category for the values. pets is name/species/level/quality; completed_quests is quest ids. Results are kept under ~20k tokens: anything left out to fit is listed in truncated_sections with the request that fetches it.

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": {
      "name": "<name>",
      "realm": "<realm>"
    },
    "name": "get_character"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCharacter name.
realmYesRealm name or slug, e.g. "Area 52" or "area-52".
regionNous
sectionsNo
achievement_idsNoWith the achievements section: completion status and date for each id, plus criteria progress for incomplete ones.
raid_expansionsNoRaid progress to include: "current" (default, the newest expansion), "all", or a list of journal expansion ids.current
achievements_limitNoPage size for achievement_category.
dungeon_expansionsNoDungeon progress to include: "current" (default, the newest expansion), "all", or a list of journal expansion ids.current
achievements_offsetNoSkip this many completions in achievement_category (page on has_more).
statistics_categoryNoWith the achievement_statistics section: return the statistics in this category (name or id).
achievement_categoryNoWith the achievements section: list completed achievements (id, name, completed date, points) in this category and its subcategories, newest first. A category name (e.g. "Midnight Raid") or id; an ambiguous name returns the matching ids.
include_cosmetic_slotsNoAlso include the shirt and tabard slots in equipment.
include_inactive_loadoutsNoAlso list every other saved loadout (all specs) as spec + talent_loadout_code.
include_mythic_plus_seasonsNoAlso list the ids of every M+ season the character has played.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / achievement_ids / maxItems
      Previous value: -50New value: +10
  2. Changed1 schema field changed
    • changedInput schema / properties / region / enum
      Previous value: -[
      -  "us",
      -  "eu",
      -  "kr",
      -  "tw",
      -  "cn"
      -]New value: +[
      +  "us",
      +  "eu",
      +  "kr",
      +  "tw"
      +]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds real behavioral context on top: this hits a live external armory, output is capped near 20k tokens, and anything dropped to fit is reported in truncated_sections. It does not mention rate limits or what happens when a character/realm cannot be resolved, which is the main remaining gap for an external-dependency read.

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?

Purpose is front-loaded in the first clause and nearly every following clause carries distinct information about a return shape or paging rule. It is a single dense block covering 20 enum sections and 14 parameters, so the length is largely justified, though per-section line breaks or grouping would make it easier to scan under time pressure.

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?

With no output schema and high parameter count, the description does the heavy lifting well: it sketches the return shape of equipment, talents, mythic_plus, achievements, pets and completed_quests, and explains truncation. It omits error behavior for unknown characters/realms and does not explain the region parameter's effect, which keeps it from a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 86%, but the description adds meaning the schema lacks: the implicit default for sections (equipment, talents, stats, mythic_plus), the fact that raids/dungeons cover only the current expansion unless expansions are named, and the interaction between achievement_category and achievements_limit/offset paging. Region, include_cosmetic_slots and include_mythic_plus_seasons are left to the schema, so it is strong rather than exhaustive.

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?

Opens with a specific verb and resource: 'Look up a live World of Warcraft character from Blizzard's armory', and immediately scopes what is returned (profile summary plus requested sections). It also names the sibling handoff (talent_loadout_code is passed to decode_build), so an agent can separate this lookup tool from decode_build, compare_character and the build-generation siblings.

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?

Gives concrete operational guidance: the default section set is stated, raid/dungeon progress is current-expansion-only with raid_expansions / dungeon_expansions for older content, and the achievements family is explicitly routed (summary vs achievement_category paging vs achievement_ids). It does not discuss when to prefer compare_character or when not to call this tool, so it falls short of full alternative routing.

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