Skip to main content
Glama

FPL Copilot

by com.fplcopilot
OverviewDiscussionsAdmin

FPL fixture difficulty

get_fixture_ticker
Read-onlyIdempotent

Use this for Fantasy Premier League fixture difficulty (FDR) and which teams have the easiest or hardest fixtures: each club's coming fixtures and their average difficulty, easiest runs first.

Input Schema

NameRequiredDescriptionDefault
gw_toNoLast gameweek. Leave empty for a 6-gameweek view (max 8 ahead)
teamsNoClubs to include (default: all 20)
gw_fromNoFirst gameweek. Leave empty for the next gameweek; set only if the user names one

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / gw_from / anyOf
      Previous value: -[
-  {
-    "maximum": 38,
-    "minimum": 1,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "maxLength": 12,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / gw_to / anyOf
      Previous value: -[
-  {
-    "maximum": 38,
-    "minimum": 1,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "maxLength": 12,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / teams / anyOf
      Previous value: -[
-  {
-    "items": {
-      "maxLength": 30,
-      "minLength": 1,
-      "type": "string"
-    },
-    "maxItems": 20,
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "maxLength": 30,
+      "minLength": 1,
+      "type": "string"
+    },
+    "maxItems": 40,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
  2. 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, lowering the bar. The description adds genuine behavioral detail by stating the ordering ('easiest runs first'), but does not describe the default window, pagination, or response shape beyond that.

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?

A single, front-loaded sentence beginning with 'Use this for' that delivers purpose, scope, and output ordering without filler. Slightly dense but no wasted sentences.

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 usefully conveys what is returned (per-club fixtures, average difficulty, ordering) and there are no required parameters to explain. It is complete for this complexity level, lacking only detail on fixture-count limits beyond what the schema states.

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 description coverage is 100%, so all three parameters (gw_from, gw_to, teams) are already documented in the schema with sensible defaults. The description adds nothing about parameter formats or interactions, so the baseline 3 is appropriate.

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 states a specific verb+resource combination ('Fantasy Premier League fixture difficulty'), plus the payload ('each club's coming fixtures and their average difficulty'). It clearly distinguishes itself from siblings like get_player or get_captain_picks, though it does not name any sibling explicitly.

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 opening 'Use this for Fantasy Premier League fixture difficulty (FDR) and which teams have the easiest or hardest fixtures' gives a clear use context. It lacks any explicit when-not or alternative-tool routing, which keeps it short of a 5.

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

All FPL Copilot toolsInspect
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