Skip to main content
Glama
MaxWilk

poe2-build-mcp

by MaxWilk

equip_item

Equip an item on an active build from raw Path of Building item text, optionally specifying the slot. Returns updated stats and flags any illegal affixes.

Instructions

Equip an item on the active build from raw Path of Building item text.

Replaces whatever is currently in the target slot. slot optionally forces the slot; otherwise the item's primary slot is used — which for a PAIRED slot is the first one, so pass an explicit slot for "Ring 2"/"Weapon 2" or it silently overwrites Ring 1/Weapon 1. Returns updated stats.

Hand-written items are checked against the real mod pool: if an affix can't roll on the base type (e.g. flat/% maximum Mana on a body armour), the result carries illegalAffixes + a legalityWarning — the computed stats then include invented mods and aren't achievable. Ground gear in real mods (optimize_item, parse_item, search_mods) to avoid this.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawYes
slotNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Since no annotations are provided, the description carries full burden. It discloses that the tool replaces the slot, returns updated stats, and checks hand-written items for legal affixes, returning illegalAffixes and legalityWarning. This fully informs the agent of side effects and edge cases.

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 multi-sentence but well-structured, with the main purpose first. Each sentence adds valuable information (replacement behavior, slot details, legality checks). Slightly verbose due to warnings, but no unnecessary fluff.

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 tool with 2 parameters and an output schema, the description covers the main behavior, return values, and a key warning about hand-written items. It does not mention error cases or prerequisites, but given the complexity, it is reasonably complete.

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

Parameters5/5

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

With 0% schema description coverage, the description adds essential meaning: it explains that 'raw' is Path of Building item text, and 'slot' optionally forces the slot, with a detailed warning about paired slots and default behavior. This goes far beyond the schema's bare property names.

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 the verb 'Equip', the resource 'an item on the active build', and the input format 'raw Path of Building item text'. It distinguishes this from sibling tools like equip_jewel and unequip_item by specifying the exact operation and source.

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 usage guidance: it replaces the current slot, explains slot inference, warns about paired slots (Ring 2/Weapon 2), and advises using explicit slot to avoid overwriting. It also distinguishes between hand-written and ground gear usage. Though it doesn't explicitly state when not to use it, the context is clear.

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