Skip to main content
Glama
rishijatia

Fantasy Premier League MCP Server

get_gameweek_status

Retrieve precise status and timing details for the current, previous, and next gameweeks to manage your Fantasy Premier League team.

Instructions

Get precise information about current, previous, and next gameweeks

Returns:
    Detailed information about gameweek timing, including exact status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual handler function for the 'get_gameweek_status' tool. It fetches gameweeks via the API, determines current, previous, and next gameweeks, computes the precise status (Upcoming, Imminent, In Progress, Complete), and returns a formatted response with gameweek IDs, season progress, and exact timing.
    async def get_gameweek_status() -> Dict[str, Any]:
        """Get precise information about current, previous, and next gameweeks
        
        Returns:
            Detailed information about gameweek timing, including exact status
        """
        gameweeks = await api.get_gameweeks()
        
        # Find current, previous, and next gameweeks
        current_gw = next((gw for gw in gameweeks if gw.get("is_current")), None)
        previous_gw = next((gw for gw in gameweeks if gw.get("is_previous")), None)
        next_gw = next((gw for gw in gameweeks if gw.get("is_next")), None)
        
        # Determine exact current gameweek status
        current_status = "Not Started"
        if current_gw:
            deadline = datetime.datetime.strptime(current_gw["deadline_time"], "%Y-%m-%dT%H:%M:%SZ")
            now = datetime.datetime.utcnow()
            
            if now < deadline:
                current_status = "Upcoming"
                time_until = deadline - now
                hours_until = time_until.total_seconds() / 3600
                
                if hours_until < 24:
                    current_status = "Imminent (< 24h)"
            else:
                if current_gw.get("finished"):
                    current_status = "Complete"
                else:
                    current_status = "In Progress"
        
        return {
            "current_gameweek": current_gw and current_gw["id"],
            "current_status": current_status,
            "previous_gameweek": previous_gw and previous_gw["id"],
            "next_gameweek": next_gw and next_gw["id"],
            "season_progress": f"GW {current_gw and current_gw['id']}/38" if current_gw else "Unknown",
            "exact_timing": {
                "current_deadline": current_gw and current_gw["deadline_time"],
                "next_deadline": next_gw and next_gw["deadline_time"]
            }
        }
  • The tool is registered using the @mcp.tool() decorator on the get_gameweek_status function at line 196 in src/fpl_mcp/__main__.py. No schema files are used; the input validation is implicit via the decorator.
    @mcp.tool()
    async def get_gameweek_status() -> Dict[str, Any]:
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 for behavioral disclosure. It only states that it returns information about gameweek timing and status, but does not mention data freshness, side effects, permissions, or any other behavioral traits. This is minimal for an unannotated tool.

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 two short sentences with no fluff. It is front-loaded with the core purpose. Every word contributes meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters and no output schema, the description is minimal but adequate for a simple retrieval tool. However, it could elaborate on the format of the returned data or any limitations (e.g., data freshness). It doesn't fully compensate for the lack of structured metadata.

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 zero parameters, and schema description coverage is 100% (trivially). With no parameters, the baseline is 4. The description adds context by specifying the scope (current, previous, next), which adds value beyond the empty schema.

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

Purpose5/5

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

The description clearly states the tool retrieves precise information about current, previous, and next gameweeks. It uses a specific verb 'Get' and resource 'gameweek status', and the scope distinguishes it from siblings like get_blank_gameweeks and get_double_gameweeks.

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. There is no mention of context, when-not-to-use, or comparative advantages. With many gameweek-related siblings, this lack of guidance is a significant gap.

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/rishijatia/fantasy-pl-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server