Skip to main content
Glama
Path of Building MCP Server

Path of Building MCP Server

by Demonad112

import_from_maxroll

Scrape a Maxroll PoE2 build planner and import it into your PoB2 builds directory as a ready-to-use .xml file with merged, switchable Tree, Item, and Skill Sets.

Instructions

Scrape a Maxroll PoE2 build planner and import it into your PoB2 builds directory. Delegates to the guide2pob Python package (pip install -e ~/repos/guide2pob). Creates a ready-to-use .xml file with all phases merged into switchable Tree specs, Item Sets, and Skill Sets.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "import_from_maxroll"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesMaxroll build planner URL, e.g. https://maxroll.gg/poe2/planner/abc123
levelNoCharacter level to record in the build (default: 90)
mergeNoMerge all build phases into one build with switchable specs (default: true)
ascendancyNoOverride the detected ascendancy name when auto-detection fails
build_nameNoOutput filename without extension (default: derived from URL slug)
class_nameNoOverride the detected class name when auto-detection fails
no_reorderNoKeep Maxroll phase order instead of sorting leveling first (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description does earn credit for disclosing the write side effect (creates a .xml in the builds directory) and the external dependency on the guide2pob package. It omits key behavior for a mutating import: overwrite semantics for build_name collisions, network/scrape failure modes, and whether partial output is left behind on failure.

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?

Three sentences, front-loaded with the action and target, then the artifact produced. The pip install path is somewhat environment-specific noise but plausibly useful for diagnosing a missing dependency.

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

Completeness3/5

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

For a seven-parameter write tool with no annotations and no output schema, the description covers purpose and output artifact but leaves gaps on destination path specifics, overwrite behavior, and error handling that an agent would need to call it safely.

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

Parameters3/5

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

Schema coverage is 100%, so all seven parameters are documented in the schema, setting a baseline of 3. The description explains the merged output shape (switchable Tree specs, Item Sets, Skill Sets), which slightly clarifies the merge parameter, but it adds nothing about level, ascendancy, class_name overrides, or no_reorder beyond what the schema already says.

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?

Names a specific verb and resource ('Scrape a Maxroll PoE2 build planner and import it into your PoB2 builds directory') and clearly scopes the source site, which distinguishes it from import_from_mobalytics and import_from_pobbin without opening their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the source name – an agent can infer to use this for Maxroll URLs, but the description gives no explicit when/when-not guidance, no prerequisites (e.g. valid planner link), and no note about what happens if a build with the same name already exists.

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