Skip to main content
Glama
Sign In
Path of Building MCP Server

Path of Building MCP Server

by urbanvcode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

gem_upgrade_path

Generate a prioritized gem upgrade shopping list that shows which gems to level, quality, or upgrade to Exceptional, ordered by impact and budget.

Instructions

Generate a prioritized gem upgrade shopping list showing which gems to level, quality, and upgrade to Exceptional versions, ordered by impact and budget

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gem_upgrade_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
budgetNoBudget tier: 'league_start', 'mid_league', 'endgame' (default: endgame)
build_nameNoBuild file (optional if loaded in Lua bridge)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/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 behavioral burden. It discloses the output content and ordering criteria (impact and budget), implying a read-only computation, but it does not state whether the operation is safe, whether it modifies the build, or what happens if no build is loaded. Adequate but with clear gaps.

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?

A single, front-loaded sentence that packs the verb, output format, content, and ordering criteria with zero wasted words. It is clear and efficient.

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?

Given two optional parameters, full schema coverage, and no output schema, the description adequately explains the tool's purpose and return content. The main gap is the missing prerequisite that a build must be either provided or loaded in the Lua bridge, which the schema hints at but the description does not reinforce.

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 coverage is 100%, and both parameters are fully documented in the schema. The description only indirectly references budget through 'ordered by impact and budget' and adds no further meaning beyond what the schema already provides, so the baseline score 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 states a specific verb ('Generate') and a concrete resource ('prioritized gem upgrade shopping list'), plus the exact content: which gems to level, quality, and upgrade to Exceptional versions. It clearly distinguishes the output from a simple analysis, though it does not explicitly name a sibling tool to contrast against.

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 implied by the output type—use this when you need an ordered shopping list for gem upgrades based on impact and budget. However, there is no explicit guidance on when to choose this over siblings like compare_gem_setups or analyze_build, nor are prerequisites stated.

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

Deploy Server

Other Tools