Skip to main content
Glama
owen-lacey

FPL MCP Server

by owen-lacey

Get Team Data

getTeamData

Retrieve comprehensive team statistics and information from the Fantasy Premier League API to analyze performance and make data-driven decisions.

Instructions

Fetch all team data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/server.ts:201-215 (registration)
    Registration of the MCP tool 'getTeamData' with empty input schema and inline handler function that calls the getTeamData helper and returns the result as JSON text content.
    server.registerTool("getTeamData", {
      title: "Get Team Data",
      description: "Fetch all team data",
      inputSchema: {}
    }, async () => {
      const data = await getTeamData();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data)
          }
        ]
      };
    });
  • Inline handler function that executes the tool logic: fetches team data using helper and formats it for MCP response.
    }, async () => {
      const data = await getTeamData();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data)
          }
        ]
      };
    });
  • Helper function that retrieves the bootstrap-static API data and extracts the 'teams' portion.
    export async function getTeamData(): Promise<Partial<FplApiObject>> {
      const data = await getBootstrapStatic();
      return {
        teams: data.teams,
      };
    }
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. 'Fetch' implies a read operation, but it doesn't disclose behavioral traits like whether this requires authentication, rate limits, pagination, or what format the data returns. The description is minimal and lacks essential context for safe invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It's appropriately sized for a simple tool, though it could be more front-loaded with additional context without sacrificing brevity.

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, no output schema, and multiple sibling tools, the description is incomplete. It doesn't explain what 'team data' includes (e.g., vs. player data), return format, or usage context, leaving significant gaps for an agent to operate effectively.

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, but that's acceptable here. Baseline is 4 for zero parameters, as the schema fully covers the absence of inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Fetch all team data' clearly states the verb ('fetch') and resource ('team data'), but it's vague about what 'all team data' encompasses. It doesn't distinguish this tool from siblings like 'getPlayerData' or 'getEntry', leaving ambiguity about 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. With siblings like 'getEntry' (likely for user-specific data) and 'getPlayerData', the description offers no context for selection, leaving the agent to guess based on tool names 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