Skip to main content
Glama
MaxWilk

poe2-build-mcp

by MaxWilk

optimize_build

Assemble a complete high-DPS build by committing to key passive tree clusters and jewels, then maximizing DPS across all gear and supports while capping resistances and meeting minimum ehp.

Instructions

Assemble a complete, engine-verified, high-DPS build for the ACTIVE archetype — the holistic optimizer that does the synthesis the greedy per-slot tools can't (STATE tool: leaves the best build LOADED in the session).

Set up the archetype first (class + ascendancy + main skill, plus a weapon base for attack skills — it's archetype-defining), then call this. It SEEDS the dominant levers from the reference set for the build's delivery, and for each runs "commit-and-max": REQUIRE the lever's tree clusters

  • nearest jewel sockets (the over-commitment greedy won't make), then maximize metric across gear (plan_gear), jewels, supports and the weapon as a whole — iterating passes times — and keeps the best build that caps resistances and meets min_ehp. Reports what it committed + the reference-set placement so it's transparent.

levers forces explicit reference lever names (omit to auto-seed). try_uniques adds a unique-item pass. crafting applies the FULL crafting system (runes + Perfect essences + corruption) to every gear slot of the winner — the "awesome gear" boost (heavier; adds ~1-2 min). uniques EQUIPS named build-defining uniques and PRESERVES them (never recrafted); if one scales damage off an attribute (e.g. Hand of Wisdom and Action → lightning per Intelligence) that attribute is auto-committed as a lever, so the search builds the unique-enabled archetype (e.g. the Int-stack) the greedy can't find on its own. archetypes (list of {class, ascendancy, skill, weapon}) also evaluates alternative configs and keeps the best. parallel spreads the search across engine subprocesses (faster, more memory). A heavy call (~1-3 min, more with crafting). The one thing it can't model is energy-meta triggers (upstream PoB); run apply_combat_profile with the build's real conditions and validate_build.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
metricNoTotalDPS
min_ehpNo
leversNo
tierNoPinnacle
passesNo
max_jewel_socketsNo
try_uniquesNo
craftingNo
uniquesNo
convergeNo
combatNo
archetypesNo
parallelNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, description carries full burden. It discloses state modification (leaves build loaded), algorithm details (seed levers, commit-and-max, iterate passes), time estimates (~1-3 min), and limitation (cannot model energy-meta triggers). Comprehensive.

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?

Description is dense and well-structured: high-level purpose, process, parameters, limitations. A bit long but each sentence adds value. Could be slightly more concise but still clear.

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

Completeness5/5

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

Given high complexity, no annotations, and 63 sibling tools, the description thoroughly covers prerequisites, state effects, parameter roles, time cost, and limitations. Output schema exists further aiding completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage, but description explains many parameters (levers, try_uniques, crafting, uniques, archetypes, parallel, passes). However, metric, min_ehp, tier, converge, and combat are not explained. Good coverage but not complete.

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?

Clearly states 'Assemble a complete, engine-verified, high-DPS build for the ACTIVE archetype', distinguishes from greedy per-slot tools, and uses specific verbs like 'synthesize' and 'commit'. Purpose is unmistakable.

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 says to set up archetype first before calling, contrasts with per-slot optimizers, and recommends follow-up with apply_combat_profile and validate_build. Provides clear when-to and what-next guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MaxWilk/poe2-build-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server