Skip to main content
Glama

Next match

next_match
Read-onlyIdempotent

A Premier League club's next match in any competition (Premier League, FA Cup, Carabao Cup, Champions League, Europa League, Conference League): opponent, competition, kick-off in UTC and UK time (plus a local time if you give a time zone), ground and the confirmed UK TV channel. If the club is playing right now it returns that game. Use this for "when do Arsenal play next?" or "who are Liverpool playing next?".

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": "next_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
clubYesA Premier League club, as people write it: "Arsenal", "Spurs", "Man Utd", "Brighton", "Forest".
timezoneNoOptional IANA time zone for an extra local kick-off time, e.g. "America/New_York". UK time is always included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/non-open-world, so the bar is lower; the description still adds real value by disclosing the return shape and the current-game fallback behavior. It omits what happens for an ambiguous or non-Premier-League club name, which would have completed the picture.

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?

Front-loads the core purpose and return fields, then usage examples. The competition list is slightly enumerative but each item earns its place by bounding scope; no filler sentences.

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 and only two simple parameters, the description supplies everything needed: scope, edge-case behavior, returned fields, and usage phrasings. Nothing material is missing for correct invocation.

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 the schema already documents both params, including colloquial club names and the IANA time zone example. The description only restates that a timezone produces an extra local time already implied by the schema, so baseline 3 applies.

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?

States a specific verb+resource (a club's next match) and enumerates the exact competitions covered plus the fields returned (opponent, competition, kick-off times, ground, TV channel). An agent can distinguish this from fixtures/results without opening another schema.

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

Usage Guidelines4/5

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

Explicitly says 'Use this for "when do Arsenal play next?"' with two example utterances, and clarifies the live edge case ('If the club is playing right now it returns that game'), which implicitly routes live lookups away from live_scores. No explicit when-not or named alternative, so not a 5.

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