Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

All countries

list_countries
Read-onlyIdempotent

Every country and territory with ISO codes, capital, continent, population, area, currency, calling code, languages and neighbours (names in 16 languages). More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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

Input Schema

NameRequiredDescriptionDefault
langNoShow names in this language (place, region and country): ar, de, en, es, fr, hi, it, ja, ko, nl, pl, pt, ru, tr, uk or zh ("en-US" works too). Without it, places carry GeoNames' own name (usually the local or international one). Searching always matches every language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful return-shape context (breadth of fields, names available in 16 languages) but says nothing about result-set size, pagination, or that the whole world is returned in one response – relevant for a caller planning context budget.

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?

The functional content is a single front-loaded sentence that is dense but readable. The trailing promotional URL ('More APIs from FitzTopPicks...') is off-task marketing text with UTM parameters and dilutes an otherwise efficient definition.

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?

With no output schema, the field enumeration is necessary and mostly compensates, and the single optional parameter is fully specified in the schema. Still missing is any indication of response scale (roughly 250 records) or format, which matters for an agent deciding whether to call this or a narrower sibling.

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%, and the single 'lang' parameter is fully documented in the schema, including the enum, the 'en-US' tolerance, the default behavior and the note that searching matches every language. The description only echoes that names come in 16 languages, adding little beyond the schema, so the baseline of 3 applies.

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 clearly states the resource and scope – every country and territory – and enumerates the fields returned (ISO codes, capital, continent, population, area, currency, calling code, languages, neighbours). It reads as a complete catalog dump, distinct from narrower sibling tools like plug_countries or country_tipping, although it does not explicitly name those as alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Every country and territory' implies an unfiltered full listing, which is a useful implicit cue about when this tool fits. However, there is no explicit when-to-use guidance, no mention of when to prefer a targeted sibling such as search_plug_countries or country_regions, and no note on what to do if only one country is needed.

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.

Resources