Skip to main content
Glama

Front of Goal

List leagues

list_leagues
Read-onlyIdempotent

Leagues and cups that have open markets, with each one's league_id, number of upcoming matches and futures markets, most active first. Use it to find the right league_id, or to answer "which leagues can I bet on?". Filter with query, e.g. a country or a league name.

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_leagues"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost leagues to return (1 to 60).
queryNoWords in the league name, e.g. "Spain", "Liga", "women".

Output Schema

NameRequiredDescriptionDefault
noteNoWhy the list is empty or cut short.
leaguesYes
total_foundYesLeagues found before the limit.

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 read-only, idempotent, open-world, non-destructive behavior, and the description correctly adds substance on top: results are ordered 'most active first' and each row carries aggregate counts, which tells the agent what a call actually yields. It says nothing about behavior when no leagues match or how the limit truncates results.

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 compact sentences, front-loaded with what is returned and its ordering, then the use case, then filtering. Every sentence carries information and there is no 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?

An output schema exists, so return values need no prose, and annotations cover the safety profile; the description fills the remaining gaps (content, ordering, purpose, filter semantics). Nothing an agent needs to select and call this tool correctly is missing.

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%, so the baseline is 3, but the description adds real meaning to `query` by showing it matches countries as well as league names ('e.g. a country or a league name'), extending beyond the schema's narrower 'words in the league name'. `limit` is left entirely to the schema.

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?

Names a specific resource (leagues and cups with open markets) and even enumerates the returned fields (league_id, upcoming match count, futures market count) plus the sort order. This makes it distinguishable from data tools like list_futures or find_matches without opening any schema.

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?

Gives explicit when-to-use framing: 'find the right league_id' and answering 'which leagues can I bet on?'. It does not name an alternative tool or state when not to use it, so it stops short of full routing guidance.

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.