Skip to main content
Glama

Fixtures

fixtures
Read-onlyIdempotent

A Premier League club's upcoming games, in date order, with kick-off times, grounds and UK TV where confirmed. Filter by competition if asked ("Chelsea's Champions League fixtures"). Default 5 games, at most 20.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "club": "<club>"
    },
    "name": "fixtures"
  }
}

Input Schema

NameRequiredDescriptionDefault
clubYesA Premier League club, as people write it: "Arsenal", "Spurs", "Man Utd", "Brighton", "Forest".
limitNoHow many games, 1 to 20 (default 5).
timezoneNoOptional IANA time zone for an extra local kick-off time, e.g. "America/New_York". UK time is always included.
competitionNoOptional: Premier League, FA Cup, Carabao Cup, Champions League, Europa League, Conference League, "Europe" (all three UEFA competitions) or "cups" (FA Cup and Carabao Cup).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds real behavior: results are date-ordered, default 5 capped at 20, UK time always included and a local time zone optionally appended, and TV data only appears 'where confirmed' (signalling it can be missing). It stops short of saying what happens with an unrecognized club name.

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?

Two tight sentences, front-loaded with the payload and output shape, followed by the filtering rule and limits. No filler or repetition.

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

Completeness5/5

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

With no output schema, the description still tells the agent what comes back (ordered games with kick-off, ground, TV) and the volume bounds, which is everything needed to call this read-only lookup correctly. No mutation, auth, or pagination concerns apply.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already documents club, limit, timezone and competition, so the baseline applies. The description only echoes the default/limit and 'filter by competition' with an example, adding little beyond the schema's own enum-like list of competitions.

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?

States a concrete resource and scope: a Premier League club's UPCOMING games in date order, with the fields returned (kick-off, ground, UK TV). This implicitly separates it from results (past) and next_match (single game), though it never names those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives one useful trigger — 'Filter by competition if asked ("Chelsea's Champions League fixtures")' — but offers no when-not guidance or comparison to next_match/results for the case where the user only wants the single next game. Usage is implied rather than framed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources