Skip to main content
Glama
Path of Building MCP Server

Path of Building MCP Server

by Demonad112

validate_build

Validates a Path of Building build's resistances, life pool, defenses, mana sustain, accuracy, and damage scaling, returning prioritized critical, warning, and info recommendations in one call.

Instructions

Comprehensive build validation: resistances, life pool, defensive layers (avoidance/mitigation/recovery), mana sustain, accuracy, flask immunities, damage scaling. Provides prioritized critical/warning/info recommendations. PREFER this over get_build_issues + analyze_defenses — it covers both in one call. Do not call all three.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "validate_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
setNoWhich skill/item set (and tree spec) to use, 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 assess the finished build. Omit to use the set the build has active.
build_nameNoBuild to validate. If omitted and Lua bridge is active, validates currently loaded build.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the return shape conceptually (prioritized critical/warning/info recommendations) and the scope of analysis. It does not explicitly state that the tool is non-mutating or describe performance cost, but "validation" plus read-style recommendations make the read-only nature strongly implied. Solid but not exhaustive.

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?

Front-loaded with the scope of validation, followed by output expectations and then the sibling routing directive. The "Do not call all three" sentence slightly restates the preceding preference statement, a minor redundancy. Otherwise dense and purposeful.

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

Completeness4/5

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

For a two-parameter, no-output-schema analysis tool, the description tells the agent what is checked, what the output looks like (prioritized severities), and how it relates to alternatives. Nothing critical is missing, though a brief note on read-only behavior or runtime cost would make it complete.

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 both parameters (set, build_name) are already well documented in the schema, including the endgame-set nuance and the Lua-bridge fallback. The description adds no parameter-level meaning beyond that, so the baseline 3 is appropriate.

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?

States a specific verb and resource ("Comprehensive build validation") and then enumerates exactly what is checked: resistances, life pool, defensive layers, mana sustain, accuracy, flask immunities, damage scaling. This makes it clearly distinguishable from siblings like analyze_defenses or validate_gem_quality without opening a schema.

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

Usage Guidelines5/5

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

Explicitly names the alternatives ("get_build_issues + analyze_defenses") and instructs the agent to prefer this tool because it covers both in one call, plus a hard exclusion ("Do not call all three"). This is exactly the when-to-use / when-not-to-use guidance an agent needs for tool routing.

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