Skip to main content
Glama

FPL Copilot

by com.fplcopilot
OverviewDiscussionsAdmin

Rate my FPL team

rate_my_team
Read-onlyIdempotent

Use this when a Fantasy Premier League (FPL, fantasy football) manager wants their team rated or reviewed, or shares their team ID or FPL link without saying more. Scores the squad 0-100 against the best possible squad over the next 5 gameweeks and lists the biggest fixes, naming the players; pass their team ID or FPL link, or the player names read from a screenshot of their team.

Input Schema

NameRequiredDescriptionDefault
captainNoCaptain's name, if known
playersNo11-15 FPL player names (e.g. read from a screenshot of their team), used when there is no team ID. Add the club to disambiguate, e.g. 'Palmer CHE'.
team_idNoThe 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.

  1. Changed2 schema fields changed
    • changedInput schema / properties / captain / anyOf
      Previous value: -[
-  {
-    "maxLength": 40,
-    "minLength": 1,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 60,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / players / anyOf
      Previous value: -[
-  {
-    "items": {
-      "maxLength": 40,
-      "minLength": 1,
-      "type": "string"
-    },
-    "maxItems": 15,
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "maxLength": 60,
+      "minLength": 1,
+      "type": "string"
+    },
+    "maxItems": 20,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
  2. First observed

TDQS

A4.1/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 real beyond-schema context: the scoring methodology (0-100 relative to the best possible squad over the next 5 gameweeks) and the shape of the response (biggest fixes, named players).

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 trigger condition, then the effect, then the input options. Two sentences with little waste, though the second sentence is long and packs three separate ideas.

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 carries the burden of describing the result and does so (score plus prioritized fixes). All three parameters are optional with no stated precedence for the ID-vs-players fallback, and the captain input is unaddressed, leaving a small gap.

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 the baseline is 3. The description restates the accepted inputs (team ID, FPL link, or player names from a screenshot) but adds no format or precedence guidance beyond the schema, and never mentions the captain parameter at all.

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 ('rate/review their team'), plus the concrete output ('scores the squad 0-100 against the best possible squad over the next 5 gameweeks and lists the biggest fixes'). This is clearly distinguishable from get_my_team and get_manager_squad, which merely retrieve a squad rather than evaluating it.

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 explicit trigger conditions: a manager wanting a rating/review, or sharing a team ID or FPL link 'without saying more' — a genuinely useful disambiguation for an ambiguous user utterance. It does not, however, name a sibling tool or state when NOT to use this one (e.g., when they only want raw squad data).

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