Skip to main content
Glama
owen-lacey

FPL MCP Server

by owen-lacey

Get Fixtures

getFixtures

Fetch all Premier League fixtures for Fantasy Premier League planning and analysis.

Instructions

Fetch all FPL fixtures

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that fetches all FPL fixtures from the official API endpoint.
    export async function getFixtures(): Promise<any> {
      const res = await fetch('https://fantasy.premierleague.com/api/fixtures/');
      return res.json();
    }
  • src/server.ts:250-264 (registration)
    MCP tool registration for 'getFixtures', including empty input schema, title, description, and wrapper handler that calls the core getFixtures function and formats response as text content.
    server.registerTool("getFixtures", {
      title: "Get Fixtures",
      description: "Fetch all FPL fixtures",
      inputSchema: {}
    }, async () => {
      const data = await getFixtures();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data)
          }
        ]
      };
    });
  • Input schema for the getFixtures tool, which takes no parameters.
    inputSchema: {}
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. While 'Fetch' implies a read operation, it doesn't disclose important behavioral traits like whether this is a paginated API, rate limits, authentication requirements, what 'all' means (historical vs upcoming), or the format/scope of returned data.

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?

The description is extremely concise - a single 4-word phrase that communicates the core purpose without any wasted words. It's perfectly front-loaded with the essential information.

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 no annotations, no output schema, and no parameters, the description is insufficient. It doesn't explain what 'FPL fixtures' are (likely Fantasy Premier League), what time range 'all' covers, the format of returned data, or how this differs from the sibling 'getFixturesForGameweek' tool.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description adds no parameter information, which is appropriate since there are no parameters to document.

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 ('all FPL fixtures'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'getFixturesForGameweek', which appears to be a more specific version of the same operation.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With a sibling tool 'getFixturesForGameweek' that likely provides filtered results, there's no indication whether this tool returns all historical fixtures, upcoming fixtures, or both, and when one should be preferred over the other.

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