Path of Building MCP Server

Overview Schema Source Related Servers Discussions Admin

compare_trees

Compare passive skill trees from two Path of Building builds to identify differences in allocated nodes and quickly see what changed between configurations.

Instructions

Compare passive skill trees between two builds, showing differences in allocated nodes

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": {
      "build1": "<build1>",
      "build2": "<build2>"
    },
    "name": "compare_trees"
  }
}

Input Schema

Name	Required	Description	Default
`build1`	Yes	First build file name
`build2`	Yes	Second build file name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Nov 13, 2026

TDQS

A3.5/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 mentions 'showing differences' but does not disclose whether the operation is read-only, error handling, or any side effects. This is minimal transparency for a tool with no annotation support.

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?

A single sentence with no superfluous words, front-loaded with the action and resource. Perfectly concise and efficiently structured.

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 description is adequately complete for a simple tool: parameters are fully covered by schema, and the output is stated as 'showing differences in allocated nodes'. However, it lacks behavioral details like error conditions or result format, and the lack of an output schema puts some burden on the description.

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?

The schema fully covers both parameters with descriptions, so the baseline is 3. The description does not add extra meaning beyond naming the two builds, and the schema already explains 'build1' and 'build2' as file names.

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: comparing passive skill trees between two builds and showing differences in allocated nodes. The verb 'compare' is specific and the resource is well-defined, distinguishing it from the broader sibling 'compare_builds'.

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?

No explicit when-to-use or alternatives are mentioned, but the description implies usage for comparing passive skill trees specifically. Without exclusions or alternative references, the agent may not know when to choose this over 'compare_builds'.

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