Skip to main content
Glama
Path of Building MCP Server

Path of Building MCP Server

by Demonad112

analyze_build

Extract stats, skills, gear, passive tree keystones and notables, archetype detection, and optimization suggestions from a Path of Building build file to evaluate and improve your character.

Instructions

Analyze a Path of Building build file and extract detailed information including stats, skills, gear, passive skill tree analysis with keystones, notables, jewel sockets, build archetype detection, and optimization suggestions

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": {
      "build_name": "<build_name>"
    },
    "name": "analyze_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
setNoWhich skill/item set (and tree spec) to analyze, by id. Builds imported from a guide store each progression step as its own set and mark set 1 (usually Act 1) active — pass the endgame set id to analyze the finished build. Omit to use the set the build has active.
build_nameYesName of the build file (e.g., 'MyBuild.xml')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It never states that the operation is read-only, whether it requires an already-imported build, how errors surface, or whether analysis is expensive. Listing the result categories gives some signal about output, but the operational behavior is largely undisclosed.

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

Conciseness3/5

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

A single front-loaded sentence names the purpose first, which is good. However, the remainder is a long, flat enumeration of output categories with no hierarchy or prioritization, reading more like a feature dump than guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two parameters and no output schema, the description reasonably covers what is returned by enumerating stats, skills, gear, tree analysis, archetype detection, and suggestions. It is incomplete on the behavioral side (read-only nature, prerequisites, error handling) and says nothing about the meaningful 'set' workflow, which the schema alone must carry.

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%, so the schema already fully documents both build_name and the nuanced 'set' parameter. The description adds nothing about parameter meaning or formatting, which is acceptable given the high coverage but is the baseline rather than added value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Analyze a Path of Building build file') and enumerates the content it extracts, so an agent knows what it produces. It does not distinguish itself from siblings like analyze_defenses, analyze_items, analyze_skill_links, or get_build_stats, whose scopes it appears to subsume, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance. Nothing tells the agent whether to call this comprehensive analyzer versus the narrower analyze_defenses/analyze_items/analyze_skill_links tools, or whether the build must be imported first. Usage is only implied by the list of extracted information.

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