Skip to main content
Glama

Get Country Leagues

get_country_leagues
Read-only

Retrieve a country's league tiers by country ID, optionally filtering by zero-based level or one-based division to identify the correct competition structure.

Instructions

Leagues of a country. level is zero-based (0 = top), division one-based (1 = top); if both are given they must agree.

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": {
      "country_id": "<country_id>"
    },
    "name": "get_country_leagues"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNo
limitNo
offsetNo
divisionNo
country_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's main contribution is the cross-field constraint that level and division must agree when both are supplied — a rule that prevents an error and is not expressed in the schema. It says nothing about ordering, pagination behavior, or completeness of 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?

Two short clauses, zero filler, and the core resource statement is front-loaded before the parameter caveat. Every phrase conveys information an agent needs.

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

Completeness2/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 not be described. But with five parameters at 0% schema coverage and no annotations beyond readOnlyHint, the description should still cover pagination (limit/offset) and clarify the relationship between level and division — instead it explains only the numbering conventions.

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 0%, so the description carries the burden and it partially delivers: it explains that level is zero-based with 0 = top and division is one-based with 1 = top, which is genuinely non-obvious. However, country_id, limit, and offset receive no explanation at all, leaving three of five parameters undocumented.

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 fragment 'Leagues of a country' names a specific resource and, combined with the required country_id, makes the retrieval target unambiguous. There is no verb and no explicit differentiation from siblings like get_countries or get_standings, which keeps it below a 5.

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?

The description never says when to use this tool versus get_countries, get_standings, or get_seasons, and gives no hint about pagination or result size. The only conditional mentioned is a validation rule ('if both are given they must agree'), not usage guidance.

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