Skip to main content
Glama

Get Country National Teams

get_country_national_teams
Read-only

Retrieve a country's senior and junior national teams along with their coaches by providing a country ID, enabling inspection of national team structures and coaching staff.

Instructions

Senior and junior national teams of a country, with coaches.

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

Input Schema

NameRequiredDescriptionDefault
country_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, so the description's only added behavioral value is clarifying payload composition: it returns teams at both senior and junior levels, with coaches attached. It says nothing about ordering, empty results for a country with no teams, or whether an invalid country_id errors or returns empty.

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?

A single short fragment with no wasted words, which is good for scanning, but the brevity comes at the cost of under-specification rather than achieved economy. Nothing important is front-loaded because nothing beyond the resource name is present.

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 return-value details need not be explained, and the tool is a simple single-parameter read. What is missing, chiefly the provenance and semantics of country_id, is small in volume but genuinely absent. Adequate for a trivial getter, though not self-sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single required parameter country_id is undocumented in both the schema and the description. The description does not state that this is a country identifier sourced from get_countries, nor what format it takes. With only one parameter, it is the one thing the description should have covered.

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?

Names the specific resource (national teams of a country) and narrows it with scope qualifiers: senior, junior, and includes coaches. This distinguishes it from get_country_leagues and get_national_team_roster. It is a noun phrase rather than a verb phrase, but the resource and scope are unambiguous.

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?

No when-to-use guidance is given. The description never says to use this before calling get_national_team_roster, nor does it mention any prerequisites or alternatives. The agent must infer usage entirely from the tool name.

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