Skip to main content
Glama

PRO11 Pro Clubs

Pro Clubs formations

list_formations
Read-onlyIdempotent

Lists the formations available in FC 27 Clubs tactics with their positions, or one formation by name (for example "4-1-2-1-2 Narrow"). Links to the PRO11 tactics board and the attacking and defensive formation guides.

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_formations"
  }
}

Input Schema

NameRequiredDescriptionDefault
formationNoOptional formation name, e.g. 4-3-3, 3-5-2 or 4-1-2-1-2 Narrow.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 needs no restating. The description adds genuinely new information — that results carry positional data and that reference links to the PRO11 tactics board and formation guides are included. It says nothing about how an unrecognized formation name is handled or how the list is ordered.

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?

Two sentences, front-loaded with the core purpose and the optional-filter behavior before the link references. The trailing sentence about external guides is slightly tangential but still earns its place as returned-content context.

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 one-optional-parameter, read-only list tool with no output schema, the description covers what is returned (formations with positions) and the filter behavior. The only real gap is error handling for invalid formation names, which is minor at this complexity.

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 parameter is fully documented, so the schema carries the load. The description confirms the parameter is an optional formation name and repeats an example format ("4-1-2-1-2 Narrow") already present in the schema, adding little beyond it.

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 and resource ("Lists the formations available in FC 27 Clubs tactics") and clarifies the two operating modes: full list versus a single formation by name. It is unambiguous against the sibling tools (archetypes, specializations, guides), though it never explicitly differentiates itself from them.

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?

The "or one formation by name" phrasing tells the agent exactly how to switch between the two behaviors, and an example name is supplied. It stops short of explicit when-not guidance or pointing to an alternative tool for related needs, so it is clear but not exhaustive.

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