Skip to main content
Glama
MaxWilk

poe2-build-mcp

by MaxWilk

optimize_item

Craft the theoretical best-in-slot rare for any gear slot, optimizing a single metric or a weighted blend of offense and defense. Respects affix pools, mod-group exclusivity, and slot limits.

Instructions

Craft the best-in-slot rare for a slot — one metric, or a weighted blend via goals.

Searches the slot's REAL craftable affix pool (from the base's mod restrictions) and greedily fills prefixes/suffixes — respecting the 3/3 limits and mod-group exclusivity. Every candidate is engine-computed. base defaults to the currently-equipped base in that slot (so a wand build stays a wand); pass it to try a different base. rolls: "realistic" (default) or "max" (idealized T1). thorough=true adds a swap pass. Returns the crafted item (equip with equip_item), the before/after numbers, and a warning if it breaks a resistance cap.

For realistic gear, pass goals — a weight map like {"TotalDPS": 0.6, "TotalEHP": 0.4} — and the craft balances offense AND defense in one piece (real endgame gear is blended). Without goals it maximizes the single metric, which strips the other axis (a TotalDPS craft carries no life/resists). A blended craft returns metricsBefore/metricsAfter per goal. Either way, re-check get_defenses after equipping.

Each result also reports attainability (per chosen affix: required ilvl + tier depth, e.g. top tier of 8) and a coarse craft effort rating — a realism check from tier depth, NOT a market price (the data has no spawn-weights). The crafted item is a theoretical best-in-slot target; verify price with get_prices. Bounded greedy search, not a global optimum.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slotYes
metricNoTotalDPS
baseNo
ilvlNo
rollsNorealistic
thoroughNo
keep_resists_cappedNo
goalsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Discloses algorithm (greedy, bounded search), respects mod restrictions, returns theoretical best-in-slot (not market price), warns about resistance caps, and reports attainability. No annotations provided, so description carries full burden—excellent transparency.

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 purpose. Though lengthy, every sentence adds value for a complex tool. Could be slightly tighter, but acceptable.

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 complexity (8 params, no schema descriptions, no annotations, output schema exists), the description covers algorithm, return values, edge cases, and cross-references. Complete for agent invocation.

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 description coverage is 0%, but description explains most parameters: slot, metric, base, rolls, thorough, goals, and partially keep_resists_capped. Ilvl is not explicitly described, but its default (82) is common. Adds significant meaning beyond schema.

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 clearly: 'Craft the best-in-slot rare for a `slot` — one `metric`, or a weighted blend via `goals`.' Specific verb+resource+scope. Though sibling tools like optimize_jewel exist, this description distinguishes item slot optimization.

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?

Provides context: when to pass goals vs. single metric, how base defaults, and recommendations to verify price with get_prices. Lacks explicit 'when not to use', but the guidance is sufficient for selection.

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