Skip to main content
Glama

PRO11 Pro Clubs

Calculate AP for a build

calculate_build_cost
Read-onlyIdempotent

Calculates the Attribute Points (AP) an FC 27 Pro Clubs archetype needs to reach target attribute values from its starting stats, the first level that has that many AP (cap 55 = 1,419 AP), which Specializations the targets unlock, and a Build Planner link with the targets loaded.

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": {
      "archetype": "<archetype>",
      "targets": "<targets>"
    },
    "name": "calculate_build_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNoOptional level to check the budget against (default 55).
targetsYesAttribute name to target value, e.g. {"Acceleration": 90, "Dribbling": 92}. Values above the cap are capped.
archetypeYesArchetype id or name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the 55-level cap equating to 1,419 AP, that target values above the cap are silently capped, and that a Build Planner link is produced — all of which affect how an agent interprets results.

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?

A single front-loaded sentence that leads with the core computation and then lists the three secondary outputs in order. It is dense but every clause corresponds to a distinct returned artifact; only the parenthetical AP cap detail is slightly buried mid-sentence.

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?

There is no output schema, and the description compensates well by enumerating exactly what comes back (AP totals, first qualifying level, unlocked Specializations, planner URL). Combined with full schema coverage and closed-world read-only annotations, an agent has enough to call and interpret it; only the absence of guidance relative to sibling tools leaves a small gap.

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 each parameter already carries its own description (level default 55, targets map with cap behavior, archetype enum), so the baseline is 3. The description reinforces that targets are attribute-name-to-value pairs measured from 'starting stats', but adds no syntax or edge-case detail beyond what the schema states.

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 names a specific verb (calculates) and precisely enumerates what is computed: AP from starting stats to targets, the first level reaching that AP, unlocked Specializations, and a Build Planner link. It is far more specific than a title restatement, but it never contrasts itself with siblings such as get_level_progression or list_specializations, so an agent cannot rule those out from the text alone.

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: the description makes clear this is a what-if cost/projection tool for a whole build, which suggests it is the right choice when you have target attribute values in hand. There is no explicit when-to-use, when-not-to-use, or named alternative, and no note about prerequisites such as needing a valid archetype id first (get_archetype/list_archetypes).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources