Skip to main content
Glama

PRO11 Pro Clubs

Compare Specialization costs

list_specializations
Read-onlyIdempotent

Lists FC 27 Pro Clubs Specializations with the PlayStyle+ each gives, its three attribute targets and the AP to unlock it from the starting stats, cheapest first. All 39, or only those of one archetype.

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

Input Schema

NameRequiredDescriptionDefault
archetypeNoOptional archetype id or name to filter by.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context — result ordering (cheapest first) and the fact that AP cost is computed relative to starting stats rather than being a raw stored value. Pagination and total-result handling are not discussed, but with a fixed set of 39 items that is a minor gap.

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 with no filler, and the most decision-relevant facts (what is returned, and the all-vs-filtered scope) are front-loaded before the ordering note.

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

Completeness5/5

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

No output schema exists, so the description must carry return-value semantics and does: it names every returned field, the sort order, and the size of the result set. For a single-optional-parameter read tool with full annotation coverage, nothing an agent needs to invoke it correctly is missing.

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% with a single enum-constrained optional parameter, so the baseline is 3. The phrase "All 39, or only those of one archetype" does clarify the default behavior when archetype is omitted, which the schema does not state, earning it a place just at the baseline rather than above it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb ("Lists") plus a specific resource (FC 27 Pro Clubs Specializations) and enumerates the returned fields: PlayStyle+, three attribute targets, AP to unlock from starting stats. The scope ("All 39, or only those of one archetype") separates it from single-entity siblings like get_archetype.

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?

Makes the two modes of use explicit — no filter returns all 39, providing an archetype narrows to one — which tells the agent how to call it in either case. It stops short of naming alternatives (e.g., when to prefer get_archetype for a single record), so no exclusion guidance is present.

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