Skip to main content
Glama
owen-lacey

FPL MCP Server

by owen-lacey

Get Entry Transfers

getEntryTransfers

Retrieve all player transfers for a specific Fantasy Premier League team using its entry ID. This tool helps FPL managers track their team's transfer history and analyze squad changes.

Instructions

Fetch all transfers of a team

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entryIdYes

Implementation Reference

  • Core handler function that performs the HTTP fetch to retrieve transfers data for the specified entry ID from the FPL API.
    export async function getEntryTransfers(entryId: number): Promise<any> {
      const res = await fetch(`https://fantasy.premierleague.com/api/entry/${entryId}/transfers/`);
      return res.json();
    }
  • src/server.ts:84-98 (registration)
    MCP tool registration for 'getEntryTransfers', defining title, description, input schema requiring entryId (number), and thin async handler that invokes the core getEntryTransfers function and returns JSON stringified response in MCP content format.
    server.registerTool("getEntryTransfers", {
      title: "Get Entry Transfers",
      description: "Fetch all transfers of a team",
      inputSchema: { entryId: z.number() }
    }, async ({ entryId }) => {
      const data = await getEntryTransfers(entryId);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data)
          }
        ]
      };
    });
  • Zod-based input schema validation for the tool, requiring a single 'entryId' parameter of type number.
    inputSchema: { entryId: z.number() }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'fetch all transfers,' which suggests a read-only operation, but doesn't cover critical aspects like whether it requires authentication, has rate limits, returns paginated results, or what format the output takes. This leaves significant gaps in understanding how the tool behaves beyond its basic function.

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 with no wasted words, making it easy to parse. It's appropriately sized for a simple tool, though it could benefit from more detail given the lack of annotations and output schema.

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 the complexity (a read operation with one parameter), no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It states the basic purpose but lacks details on behavior, parameter meaning, and output, making it insufficient for an agent to use the tool effectively without additional context.

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?

The description doesn't mention parameters, and schema description coverage is 0%, so it adds no semantic information beyond the schema. However, with only one parameter (entryId), the baseline is 3 as the schema minimally defines it as a required number, but the description fails to explain what 'entryId' represents or how it relates to fetching transfers.

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 all transfers of a team' clearly states the action (fetch) and resource (transfers of a team), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'getEntry' or 'getEntryHistory', which might also relate to team data, so it doesn't fully distinguish its specific scope.

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?

No guidance is provided on when to use this tool versus alternatives. The description implies it's for fetching transfers, but it doesn't specify prerequisites, context (e.g., for a specific entry ID), or exclusions, leaving the agent to guess based on the tool name and input schema alone.

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