Path of Building MCP Server

Overview Schema Source Related Servers Discussions Admin

compare_builds

Compare two Path of Building builds side by side to spot differences in stats, passives, gems, and items, supporting upgrade decisions.

Instructions

Compare two Path of Building builds side by side

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_builds"
  }
}

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 only says 'compare side by side' but doesn't disclose what the output looks like, whether it's a diff, whether it has side effects, or any behavioral expectations. This is a minimal tautological explanation.

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, front-loaded sentence that is easy to parse. However, it is extremely brief and omits significant behavioral details that could be included without much added length, so it's concise but not comprehensively structured.

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

Completeness2/5

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

With no output schema and no annotations, the description is expected to explain what the tool returns or any important context. It doesn't. For a comparison tool, the agent is left without any idea of what 'compare side by side' actually produces, making the tool risky to invoke.

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%, with both parameters already described as 'First build file name' and 'Second build file name'. The description adds no additional semantic detail beyond naming the two builds, so it doesn't compensate beyond the schema baseline.

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 uses a specific verb 'Compare' with a clear resource 'two Path of Building builds' and the manner 'side by side'. This clearly distinguishes it from siblings like analyze_build (single build) and compare_trees (comparing tree structures).

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

Usage Guidelines4/5

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

The context is clear: this tool is for comparing two full builds side by side. However, it doesn't explicitly mention when not to use it or name alternatives, though the intent is fairly obvious given the verb and resource.

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