Skip to main content
Glama
deepwa7er
by deepwa7er

get_stats

Retrieve computed character stats from a Path of Building build, including life, mana, resistances, DPS, and movement speed.

Instructions

Return all computed character stats from the loaded build.

These are the values Path of Building calculates: life, mana, energy shield, resistances, DPS for each skill, movement speed, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The get_stats() tool handler function (decorated with @mcp.tool()). It calls _require_build() to ensure a build is loaded, then returns a list of dicts mapping each Stat's name to its value from the build's stat list.
    @mcp.tool()
    def get_stats() -> list[dict]:
        """
        Return all computed character stats from the loaded build.
    
        These are the values Path of Building calculates: life, mana, energy shield,
        resistances, DPS for each skill, movement speed, etc.
        """
        build = _require_build()
        return [{"stat": s.name, "value": s.value} for s in build.stats]
  • The Stat dataclass used by get_stats — each stat has a 'name' (str) and 'value' (str) field.
    @dataclass
    class Stat:
        name: str
        value: str
  • _parse_stats() — parses <PlayerStat> XML elements from the PoB build XML into Stat objects that populate Build.stats, which get_stats() returns.
    def _parse_stats(root: ET.Element) -> list[Stat]:
        build = root.find("Build")
        if build is None:
            return []
        stats = []
        for elem in build.findall("PlayerStat"):
            name = elem.get("stat", "")
            value = elem.get("value", "")
            if name and value:
                stats.append(Stat(name=name, value=value))
        return stats
  • The module docstring lists 'get_stats' as a registered tool. The actual registration is via the @mcp.tool() decorator on line 75.
    """
    PoE2 MCP server.
    
    Tools:
      load_build      — decode a PoB export code or pobb.in URL
      get_stats       — computed character stats (life, mana, damage, resists, …)
      get_passives    — allocated passive nodes (with names/stats if tree data is loaded)
      get_items       — equipped items and their mods
      get_skills      — skill socket groups and gem links
      search_passives — find allocated passives matching a keyword
      search_tree     — find any node in the full passive tree (allocated or not)
    """
Behavior3/5

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

No annotations provided, so the description must carry the burden. It does not disclose side effects, rate limits, or behavior when no build is loaded. However, the tool appears to be a straightforward read operation with no destructive actions.

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?

Two sentences, front-loaded with the core action and supplemented with examples. Every sentence adds value without redundancy.

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?

Given zero parameters and the presence of an output schema, the description is complete. It explains what the tool returns and provides examples, fitting well with sibling tools.

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?

The input schema has zero parameters with 100% coverage, so the baseline is 4. The description adds no parameter info, which is acceptable since there are no parameters.

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 clearly states the tool returns computed character stats from the loaded build, listing examples like life, mana, resistances, and DPS. It uniquely identifies its purpose among siblings, which focus on items, passives, skills, etc.

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

Usage Guidelines3/5

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

The description implies use after loading a build but does not explicitly state when to use it versus alternatives. Sibling tools exist, but no guidance on when not to use or prerequisites is provided.

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/deepwa7er/poe2-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server