Skip to main content
Glama
Path of Building MCP Server

Path of Building MCP Server

by Demonad112

upload_build_to_pobbin

Upload a local PoB2 build to pobb.in and get a shareable web link plus a pob2:// deep link that opens it directly in Path of Building 2.

Instructions

Upload a local PoB2 build to pobb.in and get a shareable web link plus a pob2:// deep link that opens the build directly in Path of Building 2.

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": {
      "build_name": "<build_name>"
    },
    "name": "upload_build_to_pobbin"
  }
}

Input Schema

NameRequiredDescriptionDefault
build_nameYesBuild file name (e.g. 'MyBuild.xml')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/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 disclosure burden, and it does add real value by naming the third-party service (pobb.in), the external side effect (content published to the web), and the two return artifacts. It stops short of stating whether uploads are public/anonymous, whether network access or an account is required, whether an existing upload is overwritten, or what happens 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.

Conciseness5/5

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

One front-loaded sentence with zero filler; the action, target service, and both outputs arrive in reading order. Nothing to trim and nothing repeated from structured fields.

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 single-parameter tool with no output schema, the description covers action, destination, and return values, which is essentially everything an agent needs to decide to call it. The remaining gaps are privacy (publishing to a public site) and failure behavior, which are minor at this complexity but not trivial for an upload operation.

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%, with the single build_name parameter documented with an example filename, so the schema already does the heavy lifting. The description adds only that the build is "local," without clarifying whether build_name is a bare filename resolved from a known build directory or an arbitrary file path — the one ambiguity that would actually matter when calling it.

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 states a specific verb and resource ("Upload a local PoB2 build to pobb.in") and names both artifacts produced: a shareable web link and a pob2:// deep link. This makes the direction of the operation clear against the reverse-flow sibling import_from_pobbin without needing to open either schema.

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 phrase "local PoB2 build" — an agent can infer this is for publishing an on-disk build rather than fetching one. There is no explicit when-to-use/when-not statement and no mention of the natural alternative (import_from_pobbin) or any prerequisite such as the file existing locally.

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