Path of Building MCP Server

Overview Schema Source Related Servers Discussions Admin

get_build_stats

Extract key stats like Life, DPS, and resistances from a named build file to assess character performance and guide optimization.

Instructions

Extract specific stats from a build (Life, DPS, resistances, etc.)

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

Input Schema

Name	Required	Description	Default
`build_name`	Yes	Name of the build file

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Nov 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description must communicate behavioral traits. It only says 'Extract' without explicitly confirming read-only behavior, failure modes, or dependency on a saved build file. This leaves safety and side effects undisclosed.

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?

The description is a single, well-structured sentence that front-loads the action and includes helpful examples. It is concise without being incomplete, though it could briefly state what the function returns.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should explain return values and expected behavior. It only lists example stats and does not mention output format, error handling, or how this differs from similar tools, making it inadequate for fully informed use.

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?

The input schema already fully describes the single parameter build_name with 'Name of the build file' (100% schema coverage). The tool description adds no parameter-specific details, so the baseline of 3 is appropriate.

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 action ('Extract') and resource ('stats from a build') with concrete examples (Life, DPS, resistances). It is clear and distinct, though it does not explicitly contrast with sibling tools like analyze_build, so it stops short of a 5.

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 is provided regarding when to use this tool versus alternatives. The description lacks any mention of context, prerequisites, or exclusions, leaving the agent to infer usage from the name alone.

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