FPL Copilot

Best Wildcard or Free Hit team

get_best_chip_squad

Read-onlyIdempotent

Use this when someone wants the best FPL Wildcard or Free Hit squad for any gameweek, or the best FPL team right now, built by fplcopilot's optimiser within £100m and FPL squad rules. Not for a Bench Boost team or when to play a chip: the result links fplcopilot's Chip Strategies for that.

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

Input Schema

Name	Required	Description	Default
`gw`	No	Gameweek (default: next)
`chip`	No	wildcard or free_hit (bench_boost and triple_captain, played on the manager's own team, return where to plan them)	wildcard

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 2, 2026

changedInput schema / properties / chip / description

Previous value: -"wildcard or free_hit"New value: +"wildcard or free_hit (bench_boost and triple_captain, played on the manager's own team, return where to plan them)"

removedInput schema / properties / chip / enum

Removed value: -[
-  "wildcard",
-  "free_hit"
-]

addedInput schema / properties / chip / maxLength
```
Added value: +24
```

changedInput schema / properties / gw / anyOf

Previous value: -[
-  {
-    "maximum": 38,
-    "minimum": 1,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "maxLength": 12,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

First observedSep 30, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent, closed-world operation. The description adds useful behavioral context: the squad is built by an optimiser under a £100m budget and FPL rules, and the result links to Chip Strategies. It does not cover response shape or auth requirements, but the annotations carry the safety profile.

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, front-loaded with the primary use case and followed by a crisp exclusion. Every clause carries useful selection or constraint information, with no wasted wording.

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?

For a simple two-parameter read-only tool with full schema descriptions and clear annotations, the description provides everything an agent needs: purpose, budget/rule constraints, exclusions, and where to go for chip timing. No output schema exists, so return-value detail is not required.

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 both parameters are already well documented. The description adds a small but meaningful nuance by indicating 'any gameweek' or 'right now' when no gameweek is supplied, and by naming Wildcard and Free Hit as the relevant chip modes.

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?

The description states a specific verb and resource: generating the best FPL Wildcard or Free Hit squad, or the best FPL team right now, via fplcopilot's optimiser. It also scopes the output with £100m budget and FPL squad rules, and distinguishes the tool from Bench Boost and chip-timing use cases.

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

Usage Guidelines5/5

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

It explicitly says when to use the tool ('when someone wants the best FPL Wildcard or Free Hit squad...') and when not to use it ('Not for a Bench Boost team or when to play a chip'). It also points to fplcopilot's Chip Strategies for the excluded chip-timing case, giving clear routing guidance.

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?