Skip to main content
Glama
MaxWilk

poe2-build-mcp

by MaxWilk

solve_for

Calculate the required magnitude of a modifier to reach a specific metric target on your active build. Enter metric, target, and lever to get the exact needed value.

Instructions

Solve for the magnitude of one modifier needed to reach a stat target on the active build.

Holds the build fixed and binary-searches lever until metric reaches target — every probe is a real engine evaluation, so the answer is computed, not estimated. Example: solve_for("TotalDPS", 1000000, "increased fire damage") → "you need ≈ +N% increased Fire Damage."

lever is a named lever (e.g. "increased fire damage", "attack speed", "maximum life", "increased critical strike chance") or a raw custom-mod template containing "{}" for the magnitude (e.g. "+{} to Level of all Fire Skills"). Returns the required magnitude, or flags the target unreachable with the best achievable value (and alreadyMet if you're past it).

Scope: ONE lever, ONE (increasing) metric. It does not balance survivability or cost and reports a requirement — verify with get_defenses / evaluate_build and confirm the magnitude is attainable via search_mods / find_supports_for.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
metricYes
targetYes
leverYes
toleranceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, but description fully discloses binary search on real engine, computed result, return behavior (unreachable and alreadyMet flags), and limitations.

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?

Well-structured with topic sentence, details, example, scope, and follow-up steps. Slightly verbose with the example but largely efficient.

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?

Covers purpose, methodology, input semantics, return behavior, and post-use actions. Output schema exists but description already explains return values, making it complete.

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% coverage, but description explains lever (named or custom mod template with {}), metrics (increasing), and tolerance default. 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?

Clearly states it solves for modifier magnitude to meet a stat target. Uses specific verb-resource pair and distinguishes from siblings like optimize_passives or evaluate_build.

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?

Provides explicit when-to-use, scope (single lever, increasing metric), and when-not-to-use (no survivability/cost balancing). Gives alternatives for verification: get_defenses, evaluate_build, search_mods, find_supports_for.

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