Skip to main content
Glama

Supported competitions

list_competitions
Read-only

Lists supported competitions with aliases, teams, type, and available data surfaces (scores, fixtures, standings, brackets, markets) so you can choose the correct competition argument.

Instructions

The competitions Claudinho answers for, one per row: the alias every other tool's competition argument takes (it also takes the name or a short form), the name, the teams (nation or club), the kind (league or cup), and what each surface is (scores, next, standings, bracket, markets: offered, not-offered-yet, or not-applicable), plus current: the competition this request is for. Offline: reads the supported table, never the network. Whether an edition is in season is not listed here; the reads say so (betweenEditions).

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

Input Schema

NameRequiredDescriptionDefault
langNoLocale for dates, list titles, match status and stage words, a match timeline's kind words (Goal, Yellow card…), the empty and outage sentences, provider attribution, and commentary: en, es, pt or fr (no other value is supported). Without it, or when it is empty, the server's CLAUDINHO_LANG when that is exactly one of the four, else en. The market copy, a few notes and the disclaimer stay English
competitionNoThe competition: an alias such as premier-league, its name (Premier League) or a short form (epl), or an ESPN slug such as eng.1 (list_competitions lists the aliases). Without it: the server's CLAUDINHO_COMPETITION, else the user's saved choice (claudinho follow); with none, the answer is noCompetition

Output Schema

NameRequiredDescriptionDefault
currentYesThe competition this request is for (its competition argument, else the server's, else the user's saved choice), as every other tool's data carries it; null when nothing is chosen
competitionsYes
responseTruncatedNo
responseTruncationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.0
    • changedInput schema / properties / competition / description
      Previous value: -"The competition: an alias such as premier-league, or an ESPN slug such as eng.1 (list_competitions lists the aliases). Without it: the server's CLAUDINHO_COMPETITION, else the user's saved choice (claudinho follow); with none, the answer is noCompetition"New value: +"The competition: an alias such as premier-league, its name (Premier League) or a short form (epl), or an ESPN slug such as eng.1 (list_competitions lists the aliases). Without it: the server's CLAUDINHO_COMPETITION, else the user's saved choice (claudinho follow); with none, the answer is noCompetition"
  2. Changed1 schema field changedv0.13.1
    • changedInput schema / properties / lang / description
      Previous value: -"Locale for dates, list titles, match status and stage words, a match timeline's kind words (Goal, Yellow card…), the empty and outage sentences, provider attribution, and commentary: en, es, pt, fr (the market copy, a few notes and the disclaimer stay English; other locales fall back to en)"New value: +"Locale for dates, list titles, match status and stage words, a match timeline's kind words (Goal, Yellow card…), the empty and outage sentences, provider attribution, and commentary: en, es, pt or fr (no other value is supported). Without it, or when it is empty, the server's CLAUDINHO_LANG when that is exactly one of the four, else en. The market copy, a few notes and the disclaimer stay English"
  3. Addedv0.12.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description usefully reinforces the latter with 'Offline: reads the supported table, never the network', plus notes that each surface row is offered/not-offered-yet/not-applicable. Beyond that it adds little behavioral detail — no mention of the cost or size of the table, caching, or how 'current' is determined.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Everything is packed into a single run-on sentence dense with parentheticals, which makes it harder to scan than a short lead sentence followed by field notes. Much of its length enumerates output row fields that an output schema already defines, so a good share of the text does not earn its place.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description needn't spell out return fields — yet most of it does exactly that, while omitting guidance on the two input parameters. It does cover the offline/static nature and the deliberate gap around in-season status, leaving it adequate but misallocated for a simple two-parameter, read-only reference tool.

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 both the lang and competition inputs are fully documented in the schema itself. The description's only parameter-adjacent remark ('the alias every other tool's competition argument takes') describes output rows rather than the two inputs, so the baseline of 3 is appropriate.

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 states the resource concretely ('the competitions Claudinho answers for, one per row') and frames it as the supported/reference table, which is clearly distinguishable from the get_* sibling tools that fetch live data. It never uses a crisp verb like 'list', so the operation is inferred from the title and row enumeration rather than stated outright.

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 establishes context: the rows carry 'the alias every other tool's competition argument takes', which tells an agent to consult this before calling siblings that take a competition argument. It also adds an explicit exclusion — 'Whether an edition is in season is not listed here; the reads say so (betweenEditions)' — though no alternative tool is named for that purpose.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.