Identify upcoming blank gameweeks where Premier League teams have no fixtures, so you can plan transfers and avoid fielding incomplete squads.
Get information about upcoming blank gameweeks where teams don't have fixtures
| Name | Required | Description | Default |
|---|---|---|---|
| num_weeks | No | Number of upcoming gameweeks to check (default: 5) |
Changes observed during successful MCP inspections.
v0.1.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full behavioral burden. It indicates a read-only informational operation but does not disclose what information is returned, whether it includes all teams, or any edge cases such as gameweeks with no blank fixtures.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that front-loads the action and the target resource. Every word contributes meaning, with no filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
This is a simple one-parameter getter, so a short description is mostly adequate. However, since there is no output schema and no annotations, the description leaves unspecified what 'information' is returned, such as gameweek numbers or affected teams.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the parameter already has a clear description with a default value. The tool description adds no further parameter detail, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Get information') and a specific resource ('upcoming blank gameweeks where teams don't have fixtures'). This clearly distinguishes the tool from its sibling fpl_get_double_gameweeks by concept, though it does not explicitly name that sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied: an agent can infer this tool is for queries about blank gameweeks. However, there is no explicit when-to-use guidance, no mention of alternatives, and no exclusions, leaving some routing judgment to the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.