Skip to main content
Glama

PRO11 Pro Clubs

Archetype stats, caps and costs

get_archetype
Read-onlyIdempotent

Full FC 27 Pro Clubs data for one archetype: starting value, cap and AP cost tier of every attribute, skill moves and weak foot, Signature PlayStyles and Perks, and each Specialization with its targets and AP cost (Season 2 prices, level cap 55).

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

Input Schema

NameRequiredDescriptionDefault
archetypeYesArchetype id or name, e.g. magician, finisher, shot-stopper.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, non-open-world lookup. Beyond that, the description adds useful content transparency by enumerating the included data: attribute starting values, caps, AP cost tiers, skill moves, weak foot, PlayStyles, Perks, Specializations, targets, and costs.

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?

The definition is a single front-loaded sentence with a tight colon-separated list of included data. It contains no filler and every listed category helps an agent understand the tool's return scope.

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 read-only lookup tool with one fully documented enum parameter and no output schema, the description is largely complete: it explains what data is returned and notes season and level-cap context. The main omission is routing guidance relative to similar sibling tools.

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 the single archetype parameter is fully documented with an enum and examples. The description adds no parameter-specific semantics beyond saying the data is for one archetype, so the schema carries the parameter explanation.

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 clearly states a specific verb/resource pair: retrieving full FC 27 Pro Clubs data for one archetype. It is more specific than the bare name, but it does not explicitly distinguish itself from sibling tools such as get_archetype_meta or list_archetypes.

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 gives no guidance on when to use this tool rather than alternatives. It implies single-archetype lookup, but does not mention when to choose list_archetypes, get_archetype_meta, or calculate_build_cost.

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