Skip to main content
Glama
owen-lacey

FPL MCP Server

by owen-lacey

Get Entry History

getEntryHistory

Retrieve current and past season performance data for a Fantasy Premier League team by entering its entry ID to analyze historical results.

Instructions

Fetch this and previous season performance of a team

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entryIdYes

Implementation Reference

  • Core handler function that performs the API fetch for entry history data from Fantasy Premier League.
    export async function getEntryHistory(entryId: number): Promise<any> {
      const res = await fetch(`https://fantasy.premierleague.com/api/entry/${entryId}/history/`);
      return res.json();
    }
  • src/server.ts:67-81 (registration)
    Registers the MCP tool 'getEntryHistory' with title, description, input schema (entryId: number), and a wrapper handler that calls the core function and formats the JSON response.
    server.registerTool("getEntryHistory", {
      title: "Get Entry History",
      description: "Fetch this and previous season performance of a team",
      inputSchema: { entryId: z.number() }
    }, async ({ entryId }) => {
      const data = await getEntryHistory(entryId);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data)
          }
        ]
      };
    });
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 mentions 'fetch' but does not specify if this is a read-only operation, requires authentication, has rate limits, or what the output format might be. This lack of detail is a significant gap for a tool with no structured safety hints.

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, direct sentence that efficiently conveys the core purpose without unnecessary words. It is front-loaded and appropriately sized, 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 lack of annotations, 0% schema coverage, and no output schema, the description is incomplete. It does not address behavioral traits, parameter details, or return values, making it inadequate for a tool that retrieves historical performance data with one required 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 schema description coverage is 0%, and the description does not explain the 'entryId' parameter beyond implying it relates to a team. It fails to clarify what an 'entryId' represents, how to obtain it, or its format, leaving the parameter's meaning unclear and not compensating for the schema's lack of documentation.

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 ('this and previous season performance of a team'), making the purpose understandable. However, it does not explicitly distinguish this tool from siblings like 'getEntry' or 'getTeamData', which might also retrieve team-related information, so it falls short of a perfect 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. With siblings like 'getEntry' and 'getTeamData' available, there is no indication of specific contexts, prerequisites, or exclusions for selecting this tool over others, leaving usage ambiguous.

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