Skip to main content
Glama

Where to watch (UK)

where_to_watch
Read-onlyIdempotent

How to watch a game in the UK: the confirmed TV channel, or "TBC" when none is announced, or "not shown live in the UK" for a Saturday 3pm Premier League game; plus the radio commentary line. Give a match ("Arsenal v Chelsea", "Man City vs Real Madrid") or just a club for its next game. UK only: it does not cover other countries' broadcasters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "where_to_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
clubNoOr a club, for its next game.
matchNoA game, e.g. "Liverpool v Man Utd". The home side first if known; the next meeting is used.
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.1/5.0
Behavior4/5

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

Annotations already declare this as a safe, idempotent, closed-world read, so the lower bar is met with room to spare. The description goes further by disclosing the exact result vocabulary — 'TBC' when nothing is announced, 'not shown live in the UK' for Saturday 3pm Premier League games — plus the radio commentary line and the geographic coverage limit, all of which an agent could not infer from the annotations.

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?

One dense, front-loaded sentence plus a short scope sentence; the output cases and input flexibility come first, and the UK limitation is placed last where it belongs. The semicolon-chained enumeration is slightly heavy but every clause carries information.

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

Completeness4/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 rightly carries the burden of describing return values — channel, TBC, not-shown-live, radio line, and the always-present UK kick-off time with optional local time. For a simple 3-param lookup this is nearly complete; only edge behavior (e.g. what radio returns for a club query) is left implicit.

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 description coverage is 100%, so all three parameters are already documented, including the match format and the 'next meeting is used' rule. The description echoes the club-vs-match choice but adds no syntax or fallback detail beyond what the schema already says, so the baseline of 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?

The description opens with a specific verb+resource ('How to watch a game in the UK') and immediately enumerates the three possible outputs, which makes it unmistakable against siblings like fixtures, live_scores, or results that also concern games but not broadcast availability.

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?

It states clearly when to use it — give a match, or just a club for its next game — and adds a scope exclusion ('UK only: it does not cover other countries' broadcasters'). It stops short of naming an alternative tool for non-UK broadcast info, so it is not a full when/when-not/alternative treatment.

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