Skip to main content
Glama
deepwa7er
by deepwa7er

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TREE_DATA_PATHNoPath to an alternative passive tree JSON filedata/poe2_tree.json

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
load_buildA

Load a Path of Building export code or pobb.in share link.

Accepts:

  • A raw PoB export code (the long base64 string from File > Share > Copy code)

  • A pobb.in URL (e.g. https://pobb.in/AbCdEfGh)

Call this first before using any other tool.

get_statsA

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.

get_passivesA

Return all allocated passive nodes in the loaded build.

By default only keystones, notables, and masteries are returned — the nodes that meaningfully define the build. Set include_small_nodes=True to also include the generic small passives (+10 str, +5 life, etc.).

If tree data is not loaded, returns the raw node IDs only.

get_itemsA

Return all equipped items in the loaded build with their mods.

Each item includes slot, rarity, name, base type, item level, and the list of mod lines exactly as they appear in the game tooltip.

get_skillsA

Return all skill socket groups in the loaded build.

Each group shows the active skill, its support gems, the slot it occupies, and whether it is enabled.

search_passivesA

Search the loaded build's allocated passives for nodes matching a keyword.

Searches both node names and stat descriptions (case-insensitive). Requires tree data to be loaded; returns an error message otherwise.

Examples: search_passives("life") → all life-related nodes search_passives("fire") → fire damage nodes search_passives("Acrobatics") → the Acrobatics keystone if allocated

search_treeA

Search the full passive skill tree for nodes matching a keyword.

Unlike search_passives, this searches ALL nodes in the tree — not just those allocated in the loaded build. Use this to discover nodes you haven't taken yet.

Each result includes:

  • allocated: whether the node is already taken in the current build

  • ascendancy: the ascendancy class that unlocks this node, or "" for generic nodes

  • distance_from_build: minimum passive points needed to reach this node from the current build (null if no build is loaded or the node is unreachable)

Use classes to restrict results to one or more class regions (Voronoi partition). This eliminates nodes from the opposite side of the tree that are never reachable in practice. Valid class names: Druid, Huntress, Mercenary, Monk, Sorceress, Warrior.

A build does not need to be loaded. Tree data must be present.

Examples: search_tree("life") → all life notables across the full tree search_tree("lightning", classes=["Monk"]) → lightning nodes near the Monk start search_tree("life", classes=["Monk", "Sorceress"]) → life nodes in two regions search_tree("Invoker") → all Invoker ascendancy nodes

get_reachable_nodesA

Return all unallocated passive nodes reachable within max_distance steps from the current build.

Distance 1 = adjacent to an allocated node (can be taken with the next point). Distance 2 = one unallocated pathing node away, and so on.

Results are sorted by distance (closest first), then by type (keystones and notables before small nodes). Use this to find what is actually within reach before recommending passive picks.

Use classes to restrict results to one or more class regions, filtering out nodes from unrelated parts of the tree. Valid class names: Druid, Huntress, Mercenary, Monk, Sorceress, Warrior.

Requires both a loaded build and tree data.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 8 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: load_build is foundational, get_items/get_passives/get_skills/get_stats retrieve different build aspects, search_passives/search_tree search different scopes, and get_reachable_nodes finds nearby nodes. No overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., load_build, get_items, search_tree), making them predictable and easy for an agent to understand.

Tool Count5/5

8 tools is well-scoped for a build analysis server: loading, viewing items/passives/skills/stats, searching, and finding reachable nodes. Not too few or too many.

Completeness4/5

The tool set covers core build inspection needs comprehensively, but lacks write operations (e.g., modify passives, equip items). For a read-only analysis server, this is nearly complete.

Maintenance

ActivityInactive
ResponsivenessNo issues