FPL Copilot

Best FPL 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 FPL Copilot's optimiser within £100m and FPL squad rules. Not for a Bench Boost team or when to play a chip: the result links FPL Copilot's Chip Strategies for that.

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.3/5.0

Behavior4/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 useful behavior: the squad is constrained to £100m and FPL squad rules, produced by an optimiser, and the result links out to Chip Strategies. It stops short of describing output shape, but with no output schema and the link behavior stated, this is strong.

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?

Front-loaded with the core purpose before the exclusions, and every clause earns its place. The second sentence is slightly tangled ('the result links FPL Copilot's Chip Strategies for that'), costing it the top mark.

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 two-parameter, optional-input, read-only tool with no output schema, the description covers scope, constraints (£100m, squad rules) and the redirect path for chip timing. Minor gap: it doesn't state how the 'best right now' variant is selected when gw is omitted.

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 both parameters carry their own descriptions (gw defaulting to next, chip accepting wildcard/free_hit with a note on bench_boost/triple_captain). The description restates the chip domain but adds no syntax or default detail beyond the schema, so the baseline 3 applies.

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 and resource — the best FPL Wildcard or Free Hit squad for any gameweek or right now — plus the source ('FPL Copilot's optimiser'). It also names what it is not (Bench Boost team, chip timing), so the agent can separate it from chip-planning siblings without opening the schema.

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?

Explicit when-to-use ('someone wants the best FPL Wildcard or Free Hit squad for any gameweek, or the best FPL team right now') and an explicit when-not ('Not for a Bench Boost team or when to play a chip'), with a pointer to where chip-planning answers live. Nothing is left to inference.

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?