Skip to main content
Glama
owen-lacey

FPL MCP Server

by owen-lacey

Get Entry Picks

getEntryPicks

Fetch a Fantasy Premier League team's squad selections for a specific gameweek using entry ID and week number.

Instructions

Fetch squad picks of a team for a specific week

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entryIdYes
gwYes

Implementation Reference

  • The core handler function that fetches the Fantasy Premier League API endpoint for a manager's (entry) squad picks in a specific gameweek (gw). This is the primary implementation of the tool logic.
    export async function getEntryPicks(entryId: number, gw: number): Promise<any> {
      const res = await fetch(`https://fantasy.premierleague.com/api/entry/${entryId}/event/${gw}/picks/`);
      return res.json();
    }
  • Zod-based input schema defining the required parameters: entryId (manager/team ID) as number, gw (gameweek) as number.
    inputSchema: { entryId: z.number(), gw: z.number() }
  • src/server.ts:101-115 (registration)
    MCP tool registration including title, description, schema, and thin wrapper handler that invokes the core getEntryPicks function and formats the response as MCP content.
    server.registerTool("getEntryPicks", {
      title: "Get Entry Picks",
      description: "Fetch squad picks of a team for a specific week",
      inputSchema: { entryId: z.number(), gw: z.number() }
    }, async ({ entryId, gw }) => {
      const data = await getEntryPicks(entryId, gw);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data)
          }
        ]
      };
    });
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,' implying a read-only operation, but doesn't specify if it requires authentication, has rate limits, returns paginated data, or what the output format is. This leaves significant gaps in understanding the tool's behavior.

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 that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, 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 the complexity of a 2-parameter tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, parameter meanings, and expected outputs, failing to provide enough context for effective use by an AI agent.

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?

The schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions 'entryId' and 'gw' (gameweek) implicitly but doesn't explain what these parameters represent (e.g., entryId as a team identifier, gw as a specific week number), their formats, or constraints, adding minimal value 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 the resource ('squad picks of a team for a specific week'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'getEntry' or 'getEntryHistory', which might also relate to team data, so it misses the highest score.

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, such as needing a valid entryId and gw, or compare it to siblings like 'getEntry' for general team info or 'getElementSummary' for player details, leaving usage context unclear.

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