FPL Copilot

Captain picks

get_captain_picks

Read-onlyIdempotent

Use this when someone asks who to captain (or Triple Captain) in Fantasy Premier League (fantasy football) this gameweek. Call it even without their team: it then lists the best captain options in the game. With a team ID (or their team from an earlier chat) it ranks their own players; scope "all" ranks the game.

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

Input Schema

Name	Required	Description	Default
`scope`	No	all: the best captains in the game, for general asks; squad: from the user's own team
`team_id`	No	The manager's FPL team ID (entry ID), or any FPL link containing /entry/<id>/. Leave empty if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026

addedInput schema / properties / scope

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 24,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "all: the best captains in the game, for general asks; squad: from the user's own team",
+  "title": "Scope"
+}

First observedSep 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds the genuinely non-obvious behavior that it works with zero parameters and silently falls back to a game-wide ranking, which prevents an agent from needlessly asking for a team ID. It does not describe result shape, but that is not a contradiction.

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?

Three short sentences, front-loaded with the triggering user question, then the no-team case, then the team case. Nothing is redundant and each sentence changes how an agent would call it.

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 should hint at what comes back; it says it 'lists the best captain options' and 'ranks their own players', which is adequate but thin on what a pick includes (e.g. rationale, top-N count). Otherwise complete for a 2-optional-param read tool.

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%, so the baseline is 3. The description goes beyond the schema by spelling out the default/null behavior ('call it even without their team: it then lists the best captain options') and by describing the practical effect of scope 'all' vs a team ID, clarifying the interaction between the two parameters.

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?

States a specific verb+resource ('who to captain ... in Fantasy Premier League this gameweek') and even covers the Triple Captain variant. An agent can tell instantly that this is not find_players or get_manager_squad but a captain recommendation tool.

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?

Gives clear invocation conditions: use it on any captain question, 'call it even without their team', and with a team ID it ranks their own squad. It lacks an explicit 'use X instead when...' comparison to a sibling, but the when-to-use guidance and the pre-emption of the clarifying question are strong.

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

All FPL Copilot tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?