Skip to main content
Glama
owen-lacey

FPL MCP Server

by owen-lacey

Get Regions

getRegions

Retrieve the list of available regions for Fantasy Premier League data access and filtering.

Instructions

Fetch FPL region list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/server.ts:152-166 (registration)
    Registration of the MCP 'getRegions' tool. Includes schema (empty inputSchema), title, description, and a thin wrapper handler that calls the getRegions helper and formats the response as MCP content.
    server.registerTool("getRegions", {
      title: "Get Regions",
      description: "Fetch FPL region list",
      inputSchema: {}
    }, async () => {
      const data = await getRegions();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data)
          }
        ]
      };
    });
  • Core handler function implementing the getRegions tool logic by fetching the regions data from the Fantasy Premier League API and returning the parsed JSON.
    export async function getRegions(): Promise<any> {
      const res = await fetch('https://fantasy.premierleague.com/api/regions/');
      return res.json();
    }
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 states 'Fetch' implying a read operation, but doesn't disclose behavioral traits such as whether it requires authentication, has rate limits, returns a list format, or if it's idempotent. This is a significant gap for a tool with zero annotation coverage.

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 a single, efficient sentence ('Fetch FPL region list') with zero waste. It's front-loaded and appropriately sized for a simple tool, making it easy to parse quickly.

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?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what 'FPL region list' entails (e.g., structure, use cases) or behavioral aspects like response format. For a tool with rich context signals (0 params, 100% schema coverage), it should provide more guidance on output and usage.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, which is appropriate here. Baseline is 4 for zero parameters, as the schema fully handles the lack of inputs.

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 'Fetch FPL region list' clearly states the verb ('Fetch') and resource ('FPL region list'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'getLeagueStandings' or 'getPlayerData', which also fetch different data types from the same FPL system, so it lacks explicit sibling distinction.

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. It doesn't mention prerequisites, context (e.g., for user registration or data filtering), or compare to siblings like 'getLeagueStandings' for league-specific data, leaving usage unclear beyond the basic purpose.

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