Skip to main content
Glama

Get Countries

get_countries
Read-only

Retrieve every country available in BuzzerBeater so you can reference national associations in team, player, match, and market data.

Instructions

Every country available in BuzzerBeater.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the description's burden is reduced. However, it adds no behavioral context beyond the annotations: no statement about ordering, whether results are cached/static, how large the list is, or how country identifiers are formatted for downstream calls.

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?

It is a single short fragment with no wasted words, but the brevity comes at the cost of specification rather than being disciplined concision. A short complete sentence stating the tool returns the full country list used as identifiers elsewhere would fit the same space.

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?

The tool is simple (zero parameters, output schema present, so return values need no explanation), and for that complexity the fragment is minimally adequate. It still omits the one piece of context that matters for a lookup tool: what the returned countries are used for and how their identifiers feed the country-scoped siblings.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies no filtering arguments are needed to retrieve the complete set.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Every country available in BuzzerBeater" conveys the resource (countries) and that the list is complete, but it is a noun fragment with no verb and reads close to a restatement of the name get_countries. It does not distinguish this reference list from siblings like get_country_leagues or get_country_national_teams, which take a country as input.

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 when-to-use guidance at all: nothing says this is a lookup/reference call to resolve country IDs before calling get_country_leagues, get_country_national_teams, or search_market_players. No alternatives or exclusions are named, so the agent must infer usage entirely from the name.

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