Skip to main content
Glama
Path of Building MCP Server

Path of Building MCP Server

by Demonad112

analyze_skill_links

Analyze a Path of Building skill gem setup to rate support gems, detect build archetype, and identify issues.

Instructions

Analyze skill gem setup and evaluate support gem choices. Detects build archetype, rates each support gem, and identifies issues with current setup.

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": "analyze_skill_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
setNoWhich skill/item set (and tree spec) to use, by id. Builds imported from a guide store each progression step as its own set and mark set 1 (usually Act 1) active — pass the endgame set id to assess the finished build. Omit to use the set the build has active.
build_nameYesBuild to analyze
skill_indexNoWhich skill to analyze (0 = main skill, default: 0). Indexes within the active set only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It usefully lists the analysis outputs (archetype detection, per-support-gem ratings, issue identification), but it does not state whether the build is modified, whether the operation is read-only, or any permission/rate-limit constraints.

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?

Two front-loaded sentences with no filler. The first sentence states the action and evaluation target; the second adds concrete analysis outputs without redundancy.

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 three-parameter analysis tool with a fully described input schema and no output schema, the description is largely complete: it says what is analyzed and what kinds of results are produced. It is missing side-effect disclosure and explicit sibling routing, which prevents a top score.

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%, and the description adds no parameter-level meaning beyond the existing schema. The baseline for fully documented parameters is 3 when the description does not compensate or extend parameter semantics.

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?

States a specific verb and resource: analyzing skill gem setup and evaluating support gem choices. It also names concrete outputs (build archetype, support gem ratings, issues), but it does not explicitly distinguish itself from optimization siblings like optimize_skill_links or compare_gem_setups.

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

Usage Guidelines2/5

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

The description explains what the tool does but gives no explicit when-to-use, when-not-to-use, or alternative-tool guidance. Use for assessing an existing setup is only implied, and there is no routing against optimization or comparison siblings.

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