Skip to main content
Glama
Path of Building MCP Server

Path of Building MCP Server

by Demonad112

find_optimal_links

Generates an optimized support gem combination for a skill based on budget, link count, and goal, then provides a step-by-step upgrade path.

Instructions

Auto-generate the best support gem combination for a skill based on budget and optimization goal. Provides step-by-step upgrade path.

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>",
      "link_count": "<link_count>"
    },
    "name": "find_optimal_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
budgetNoBudget tier: 'league_start', 'mid_league', or 'endgame' (default: 'endgame')
build_nameYesBuild to optimize
link_countYesNumber of links (4, 5, or 6)
skill_indexNoWhich skill to optimize (default: 0)
optimize_forNoOptimization target: 'dps', 'clear_speed', 'bossing', or 'defense' (default: 'dps')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It reveals that output includes a step-by-step upgrade path, which is useful, but it never says whether the tool only recommends or also mutates the saved build, whether it reads the stored build by name, or how expensive/long the optimization is, which matters given the 'optimal combination' search implied.

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?

Two sentences, front-loaded with the core action and followed by the output shape; nothing is redundant. It is slightly under-specified rather than bloated, but structurally clean.

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?

With five parameters, no annotations, and no output schema, the description should say more. It covers the purpose and hints at the return value, but leaves open whether the build must be loaded first and whether any state changes occur.

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 defaults documented for budget, skill_index, and optimize_for, so the schema already does the heavy lifting. The description adds nothing about parameter meaning beyond the schema, which is acceptable at full coverage but earns no extra credit.

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: 'Auto-generate the best support gem combination for a skill' with budget and goal as inputs, plus a step-by-step upgrade path. However, it gives no hint of how it differs from close siblings like optimize_skill_links, analyze_skill_links, compare_gem_setups, or gem_upgrade_path, so the agent cannot disambiguate from the description alone.

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?

No guidance on when to use this over optimize_skill_links or compare_gem_setups, and no stated prerequisites such as whether the build must already exist in storage. The only usage-adjacent information is the mention of budget and optimization goal as the driving inputs, which is implied by the parameters anyway.

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