Skip to main content
Glama
rishijatia

Fantasy Premier League MCP Server

by rishijatia
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

analyze_fixtures

Analyze upcoming fixtures for any player, team, or position. Get difficulty ratings, blank and double gameweek info for a specified number of gameweeks.

Instructions

Analyze upcoming fixtures for players, teams, or positions

Args:
    entity_type: Type of entity to analyze ("player", "team", or "position")
    entity_name: Name of the specific entity
    num_gameweeks: Number of gameweeks to look ahead
    include_blanks: Whether to include blank gameweek info
    include_doubles: Whether to include double gameweek info
    
Returns:
    Fixture analysis with difficulty ratings and summary

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_typeNoplayer
entity_nameNo
num_gameweeksNo
include_blanksNo
include_doublesNo

Tool Definition Quality

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided. The description only mentions return format ('difficulty ratings and summary') without disclosing behavioral traits like side effects, authentication needs, or read-only nature.

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?

Well-structured with Args and Returns sections, front-loading key info. Slightly verbose but every sentence adds value.

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?

Covers parameters well but lacks details on output structure and usage context. Given 5 parameters and no output schema, the description could be more complete.

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?

Schema description coverage is 0%, so the description's docstring adds meaning for all five parameters. However, it could specify allowed values for entity_type more precisely (though not enforced in 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 verb 'Analyze' and resource 'upcoming fixtures' with scope options (players, teams, positions). However, it does not distinguish from sibling tool 'analyze_player_fixtures', which may cause confusion.

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 on when to use this tool versus alternatives like 'analyze_players' or 'compare_players'. The description lacks context for selection among siblings.

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