Skip to main content
Glama

How to watch a competition in a country

watch_competition
Read-onlyIdempotent

Who holds the rights to a football competition in a country this season, the cheapest verified monthly price (each with source and date checked), and links to the country page and the price comparison. Prices are only returned when verified within the last 90 days.

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": {
      "competition": "<competition>",
      "country": "<country>"
    },
    "name": "watch_competition"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesCountry name or ISO code.
competitionYese.g. 'Premier League', 'La Liga', 'Champions League'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open world), so the description earns credit for going further: it discloses the 90-day verification window and warns that prices are only returned when freshly verified, which tells the agent results may be partially empty. It adds useful provenance context (source and date checked) but says nothing about coverage gaps for competitions with no rights data at all.

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?

A single dense sentence that front-loads the core answer (rights holder) and appends the qualifiers. Every clause carries information — price, verification, links — though the trailing 'links to the country page and the price comparison' is slightly run-on and could be tighter.

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 steps in to describe the return payload (rights holder, price with source and date, links) and the freshness rule, which is exactly what an agent needs to interpret results. It falls short only on how to disambiguate against the sibling where_to_watch and on what an empty/unverified result looks like.

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 both parameters carry inline descriptions with examples, so the schema does the heavy lifting and baseline 3 applies. The description implies country and competition semantics (season, per-country rights) but adds no format, normalization, or disambiguation guidance beyond the schema.

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?

The description frames a specific question — who holds the rights to a named competition in a named country this season — and enumerates what comes back (rights holder, cheapest verified monthly price, source/date, links). The resource is unambiguous even though it is phrased as an answer rather than a verb. It does not, however, distinguish itself from the sibling where_to_watch, which reads as overlapping in scope.

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

Usage Guidelines2/5

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

There is no explicit statement of when to use this versus the closely-named sibling where_to_watch, nor any exclusion or prerequisite. The only scoping signal is implicit in the two required parameters (competition + country). An agent facing 'how do I watch X in Y' has to guess between this and where_to_watch.

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