Skip to main content
Glama
owen-lacey

FPL MCP Server

by owen-lacey

Get Entry

getEntry

Fetch Fantasy Premier League team information by entering a specific entry ID to retrieve general team details and statistics.

Instructions

Fetch general info about a team by entry ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entryIdYes

Implementation Reference

  • The core handler function that fetches the team entry data from the Fantasy Premier League API endpoint `/api/entry/{entryId}/` and returns the JSON response.
    export async function getEntry(entryId: number): Promise<any> {
      const res = await fetch(`https://fantasy.premierleague.com/api/entry/${entryId}/`);
      return res.json();
    }
  • src/server.ts:284-298 (registration)
    Registers the 'getEntry' MCP tool, defining its input schema (entryId: number), metadata, and a thin wrapper handler that invokes the core getEntry function and formats the response as MCP content.
    server.registerTool("getEntry", {
      title: "Get Entry",
      description: "Fetch general info about a team by entry ID",
      inputSchema: { entryId: z.number() }
    }, async ({ entryId }) => {
      const data = await getEntry(entryId);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data)
          }
        ]
      };
    });
  • Input schema validation using Zod: requires an entryId as a number.
    inputSchema: { entryId: 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 the full burden of behavioral disclosure. It states 'Fetch general info,' implying a read-only operation, but doesn't specify permissions, rate limits, error handling, or what 'general info' includes (e.g., team name, points). This leaves significant gaps for an agent to understand how to use it effectively.

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, making it easy to parse and front-loaded with key 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?

Given the lack of annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't clarify what 'general info' entails, how results are structured, or any behavioral traits, leaving the agent with insufficient context for a read operation with one parameter.

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 input schema has 1 parameter with 0% description coverage, and the description doesn't add any meaning beyond 'by entry ID.' It doesn't explain what an entry ID is, its format, or where to find it, failing to compensate for the low schema coverage.

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 ('general info about a team by entry ID'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'getEntryHistory' or 'getEntryPicks', which likely provide more specific data about the same entry.

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. With siblings like 'getEntryHistory' and 'getEntryPicks' that might offer more detailed or historical data, the description lacks context on whether this tool is for basic overviews or when other tools are more appropriate.

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