Skip to main content
Glama
Path of Building MCP Server

Path of Building MCP Server

by Demonad112

import_from_mobalytics

Scrapes a Mobalytics PoE2 build guide and imports it as a ready-to-use PoB2 .xml file you can analyze or load.

Instructions

Scrape a Mobalytics PoE2 build guide and import it into your PoB2 builds directory. Delegates to the guide2pob Python package which must be installed (pip install -e ~/repos/guide2pob). Creates a ready-to-use .xml file you can immediately open with analyze_build or lua_load_build.

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_mobalytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesMobalytics build URL, e.g. https://mobalytics.gg/poe-2/builds/my-build
levelNoCharacter level to record in the build (default: 90)
mergeNoMerge all build variants into one build with switchable Tree specs, Item Sets, and Skill Sets (default: true)
variantNoWhich variant to import when merge=false: '0', '1', '2', ... (default: '0')
ascendancyNoOverride the detected ascendancy name (e.g. 'Lich') when auto-detection fails
build_nameNoOutput filename without extension (default: derived from URL slug)
class_nameNoOverride the detected class name (e.g. 'Witch') when auto-detection fails
no_reorderNoWhen merge=true, keep Mobalytics variant order instead of sorting leveling first (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does usefully disclose the external dependency ('delegates to the guide2pob Python package... pip install -e ~/repos/guide2pob') and the output artifact, but says nothing about network/scraping failure modes, whether an existing file with the same build_name is overwritten, or how auto-detection failure surfaces beyond the class_name/ascendancy overrides.

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 front-loaded sentences: purpose first, prerequisite second, resulting artifact third. The hardcoded local path in the pip command is environment-specific but genuinely useful for setup.

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 an 8-parameter write/import tool with no annotations and no output schema, the description covers what it does, its dependency, and what it emits. It remains thin on overwrite semantics and error behavior, which matter for a file-creating tool.

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 description coverage is 100%, so all eight parameters including merge/variant interaction and defaults are already documented in the schema. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Scrape a Mobalytics PoE2 build guide and import it into your PoB2 builds directory') and the artifact it produces (.xml), which distinguishes it from the Maxroll and pobbin import siblings by source. It stops short of naming those siblings explicitly, so the differentiation is inferential rather than stated.

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: it is the tool for Mobalytics guides, and the description suggests following up with analyze_build or lua_load_build. There is no explicit 'use import_from_maxroll for Maxroll links' style routing and no statement of when not to use it.

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