Skip to main content
Glama

Live scores

live_scores
Read-onlyIdempotent

Scores of Premier League games in play right now, plus any FA Cup, Carabao Cup or European game a Premier League club is playing. When nothing is in play it gives the next Premier League kick-off.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 establish this is a safe, read-only, idempotent query, so the bar is lower. The description adds real behavioral context beyond them: the result set spans multiple competitions when a Premier League club is involved, and the tool degrades to the next kick-off rather than returning nothing.

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 sentences with no filler, and the primary case (live scores) is front-loaded ahead of the fallback case. Every clause carries distinct 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?

For a zero-parameter read tool, the description covers scope, cross-competition behavior, and the empty-state. Return shape is not described, which is a minor gap given no output schema exists, but the semantic content of the response is adequately conveyed.

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?

The tool takes no parameters, so there are no semantics to clarify; baseline applies.

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 specific resource and a precise scope: Premier League games in play now, plus cup/European games involving Premier League clubs, and a defined fallback (next kick-off) when nothing is live. This distinguishes it from fixtures/results by time state, 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 Guidelines4/5

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

Usage is clear from the scope definition ('in play right now') and the empty-state behavior is spelled out, which tells the agent what to expect instead of live data. It stops short of explicitly saying when to prefer results, fixtures, or next_match, but the live-only framing is unambiguous.

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