Path of Building MCP Server

Overview Schema Source Related Servers Discussions Admin

analyze_build

Analyze Path of Building build files to extract stats, skills, gear, passive tree keystones, notables, jewel sockets, archetype detection, and optimization suggestions.

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

Name	Required	Description	Default
`build_name`	Yes	Name of the build file (e.g., 'MyBuild.xml')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Nov 13, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It lists the types of information extracted but does not state whether the operation has side effects, requires specific permissions, or how it handles missing or invalid files. The read-only nature is implied but not explicitly stated.

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?

The description is a single sentence that front-loads the action and lists the key outputs. It is somewhat long but information-dense, with no wasted words. The structure is appropriate for the tool's broad scope.

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?

The tool is complex with many output categories, and there is no output schema or annotations to supplement the description. The description lists the types of information extracted, but does not explain the return format, potential errors, or how to interpret the results. While adequate for a basic understanding, it leaves gaps for a user needing to know what to expect.

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 coverage is 100%, so the parameter is well-documented in the schema. The description adds no additional meaning about the build_name parameter beyond what the schema provides, meeting the baseline for high 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 description clearly states the tool's function: 'Analyze a Path of Building build file and extract detailed information.' It specifies the resource (build file) and the scope (stats, skills, gear, passive tree, keystones, etc.), which distinguishes it from sibling tools by covering a comprehensive analysis rather than a single metric.

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?

The description provides no guidance on when to use this tool versus alternatives like get_build_stats or analyze_defenses. It does not mention any exclusions, prerequisites, or contexts where a different tool would be more appropriate.

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