Skip to main content
Glama
Path of Building MCP Server

Path of Building MCP Server

by Demonad112

import_from_pobbin

Downloads a shared Path of Building build from pobb.in using a full URL or bare build ID and saves it to your builds directory for PoE1 or PoE2.

Instructions

Download a shared Path of Building build from pobb.in by URL or build ID and save it to your builds directory. Accepts a full URL (https://pobb.in/AbCdEfGh) or a bare ID. Works for both PoE1 and PoE2 builds.

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_or_id": "<url_or_id>"
    },
    "name": "import_from_pobbin"
  }
}

Input Schema

NameRequiredDescriptionDefault
url_or_idYesFull pobb.in URL (https://pobb.in/<id>) or bare build ID (e.g. AbCdEfGh)
build_nameNoOutput filename without extension (default: the pobb.in build ID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key side effect: the build is written to the builds directory. However, it omits what happens on an invalid ID, network failure, or when a file with the same name already exists (overwrite vs. error), and does not describe the response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: the action and destination come first, then accepted input forms, then game-version scope. No filler and nothing buried at the end.

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 two-parameter import tool with complete schema coverage and no output schema, the description covers the essential behavior. The remaining gap is error and duplicate-file handling, which an agent would want before invoking it repeatedly.

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 both parameters are already fully documented with examples, and the description's URL/ID examples only restate them. It adds no format constraints, validation rules, or default behavior beyond what the schema provides.

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 names a specific verb (download/import), a specific resource (a Path of Building build from pobb.in), and the destination (your builds directory). It is clearly distinguishable from the sibling importers import_from_maxroll and import_from_mobalytics by naming the source site.

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?

It states the accepted input forms (full URL or bare ID) and which game versions are supported, giving clear context for when this tool applies. It does not explicitly route the agent to the other import_* tools for other sources, so a 4 rather than a 5.

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