Skip to main content
Glama

PRO11 Pro Clubs

AP and rewards by level

get_level_progression
Read-onlyIdempotent

FC 27 Pro Clubs archetype levels: AP gained at each level, running total and unlocks (PlayStyle slots, Signature Perks, PlayStyle+ upgrades, Masteries). The level cap is 55 (1,419 AP) since Season 2. Give a level for one row, or nothing for the whole table.

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

Input Schema

NameRequiredDescriptionDefault
levelNoOptional level from 1 to 55.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely non-structured context: the level cap of 55 and the 1,419 AP total, plus the 'since Season 2' data-version note, which tells the agent the data is patch-dependent. It does not describe row ordering or whether unlock fields can be empty.

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?

Two sentences, both load-bearing: the first defines the data and its columns, the second gives the cap/version and the calling convention. The subject is front-loaded and there is no filler or repetition of the schema.

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?

With no output schema, the description carries the burden of explaining return values, and it does so by enumerating the row contents and the unlock categories, plus the hard cap. Safety and idempotency are covered by annotations. Minor omission: row ordering and how a single-level request differs in shape from the full table.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already says 'Optional level from 1 to 55', so the baseline is 3. The description goes beyond it by explaining the semantic consequence of the parameter: supplying a level narrows the result to a single row, omitting it returns the full table. That meaning is not derivable from the schema alone.

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 the resource precisely ('FC 27 Pro Clubs archetype levels') and enumerates the exact payload: AP gained per level, running total, and unlocks (PlayStyle slots, Signature Perks, PlayStyle+ upgrades, Masteries). That is far more specific than a restatement of the name. It stops short of contrasting itself with siblings like calculate_build_cost, so it is clear but not sibling-differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Give a level for one row, or nothing for the whole table' gives concrete, actionable guidance on the two calling modes and when each applies. There is no explicit when-not-to-use clause or named alternative for related questions (e.g., build cost calculation), which keeps it out of the top band.

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