Skip to main content
Glama
MaxWilk

poe2-build-mcp

by MaxWilk

craft_item

Craft best-in-slot items using runes, essences, and corruptions. Specify metrics or goals to generate optimized gear with step-by-step crafting instructions.

Instructions

Craft the best-in-slot item using the FULL crafting system — beyond a plain rare.

Where optimize_item crafts the best rare from the standard affix pool, this adds the three real PoE2 power sources, each valued on the engine (PoB owns the crafting data — nothing is invented): runes / soul cores (mods socketed on top of the affixes), essences (force a mod — Perfect essences grant mods the normal pool can't roll, e.g. % Life on body armour, "damage as extra" on weapons), and corruptions (a corrupted implicit, e.g. +1 to all skills on an amulet). Pass a single metric or a weighted goals blend; rune_sockets is how many the base is assumed to support (Artificer's Orb — martial weapons/armour typically allow up to 2). Returns the item + the craftSteps to make it (the corruption is a Vaal gamble — do it last). A theoretical best-in-slot target with idealized rolls; price the steps. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slotYes
metricNoTotalDPS
baseNo
goalsNo
rollsNorealistic
rune_socketsNo
use_essencesNo
use_corruptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description carries full burden. It reveals the tool is read-only, returns item and craftSteps, and describes the gambling nature of corruption. It explains the inclusion of runes, essences, and corruptions, but does not detail all potential side effects or limitations beyond 'theoretical best-in-slot with idealized rolls.'

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 somewhat lengthy but well-structured: first sentence states purpose, then details the extra systems, then explains key parameters and return. It front-loads the core idea and maintains clarity, though some sentences could be more concise.

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?

Given the tool's complexity (8 params, 1 required, output schema present), the description covers the main aspects: tool purpose, key parameters, return format (item + craftSteps), and behavioral notes (read-only). The required 'slot' parameter is not explained, but its purpose is implied. Overall, it provides sufficient context for an agent to use the tool correctly.

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?

Despite 0% schema description coverage, the tool description adds significant meaning: it explains rune_sockets, distinguishes metric vs goals, and mentions essences/corruptions. However, parameters like 'base' and 'rolls' are not explicitly described. Overall, it compensates well for missing schema descriptions.

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 it crafts the best-in-slot item using a full crafting system beyond a plain rare, distinguishing itself from optimize_item by adding runes/essences/corruptions. The verb 'craft' and resource 'best-in-slot item' are specific, and it explicitly contrasts with a sibling tool.

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 description provides clear guidance on when to use this tool (for full crafting beyond rare optimization) and explains key parameters (metric/goals, rune_sockets). It compares directly to optimize_item, offering context, but does not list all alternatives or explicitly state when not to use.

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