Skip to main content
Glama
owen-lacey

FPL MCP Server

by owen-lacey

Get League Standings Page

getLeagueStandingsPage

Retrieve a specific page of league standings for Fantasy Premier League competitions with over 50 teams by providing league ID and page number.

Instructions

Fetch a page of league standings for leagues with more than 50 teams

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
leagueIdYes
pageYes

Implementation Reference

  • The core handler function implementing the tool logic: fetches the paginated league standings page from the Fantasy Premier League API.
    export async function getLeagueStandingsPage(leagueId: number, page: number): Promise<any> {
      const res = await fetch(`https://fantasy.premierleague.com/api/leagues-classic/${leagueId}/standings/?page_standings=${page}`);
      return res.json();
    }
  • src/server.ts:135-149 (registration)
    MCP tool registration for 'getLeagueStandingsPage', including title, description, Zod input schema, and thin wrapper handler that invokes the core function and returns formatted response.
    server.registerTool("getLeagueStandingsPage", {
      title: "Get League Standings Page",
      description: "Fetch a page of league standings for leagues with more than 50 teams",
      inputSchema: { leagueId: z.number(), page: z.number() }
    }, async ({ leagueId, page }) => {
      const data = await getLeagueStandingsPage(leagueId, page);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data)
          }
        ]
      };
    });
  • Zod schema defining input parameters: leagueId (number) and page (number).
    inputSchema: { leagueId: z.number(), page: z.number() }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions fetching a 'page' (implying pagination) and the league size condition, but lacks details on permissions, rate limits, response format, or error handling for a read operation.

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?

Single sentence, front-loaded with key information, no wasted words. It efficiently conveys the core purpose and constraint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It lacks parameter explanations, behavioral details, and output information, making it inadequate for full understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It doesn't explain what 'leagueId' or 'page' represent (e.g., format, valid ranges, or that 'page' likely starts at 1). No parameter details are provided beyond the schema.

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 clearly states the action ('Fetch') and resource ('a page of league standings'), specifying it's for leagues with more than 50 teams. It distinguishes from the sibling 'getLeagueStandings' by indicating pagination, but doesn't explicitly contrast them.

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

Usage Guidelines3/5

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

It implies usage for large leagues (>50 teams) where pagination is needed, but doesn't explicitly state when to use this versus 'getLeagueStandings' or other alternatives, nor provide exclusions or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/owen-lacey/fpl-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server