Skip to main content
Glama

Referees

referees
Read-onlyIdempotent

The match officials the Premier League has appointed for a matchweek: referee, VAR, assistant VAR, assistants and fourth official for each game. Without a matchweek it returns the latest published list. Appointments come out on the Monday of the match week, so a later matchweek says it is not published yet.

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

Input Schema

NameRequiredDescriptionDefault
matchweekNoOptional matchweek number, 1 to 38.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds genuine non-schema behavior: the Monday publication cadence and the resulting 'not published' outcome for future matchweeks, which an agent needs in order not to misinterpret an empty/negative response as an error.

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?

Three tight sentences, front-loaded with what is returned and the per-game role breakdown, then default behavior, then the timing caveat. Nothing is repeated from the schema and no sentence is filler.

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?

There is no output schema, and the description compensates by naming the returned fields per game. Combined with the default and publication-timing semantics, an agent has everything needed to call it and interpret a 'not published yet' result.

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 coverage is 100% and the single parameter is already documented with its 1-38 bounds, so the baseline is 3. The description earns one above baseline by giving the omitted-parameter semantics (returns the latest published list), which the schema does not state.

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?

Specific verb+resource: returns the appointed match officials for a matchweek, and it enumerates the roles (referee, VAR, assistant VAR, assistants, fourth official). No sibling in the list covers officials, so an agent can route here without ambiguity.

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?

States the default path (omit matchweek -> latest published list) and the practical constraint that a later matchweek may report 'not published yet' until the Monday of that week. No explicit alternatives are named, but none of the siblings plausibly overlap, so the guidance is sufficient for correct invocation.

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