Skip to main content
Glama

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

States and provinces of a country

country_regions
Read-onlyIdempotent

The first-level regions (states, provinces, cantons...) of a country with their codes, usable to narrow find_city. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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": "<country>"
    },
    "name": "country_regions"
  }
}

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.
countryYesISO 3166-1 alpha-2 code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered and the description needn't restate it. The description adds that results carry region codes (useful, since that's the key consumed by find_city) but says nothing about result size, ordering, or behavior for an unknown country code. Adequate but not rich beyond the structured data.

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 first sentence is tight and front-loaded, but the second sentence is a promotional API-catalog link with UTM parameters that adds no information for tool selection. Roughly half the description is advertising.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read lookup with no output schema, the description covers the resource, the granularity, and the included fields. Only minor gaps remain (ordering, whether all regions are returned), and there is no output schema, so return-shape detail would have helped but isn't strictly required.

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 100%: the country parameter is documented as an ISO 3166-1 alpha-2 code and the lang parameter has a full enum plus a long explanation. The description's only parameter-adjacent contribution is "of a country," which restates the schema rather than adding format or edge-case detail. Baseline 3 is appropriate.

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?

"The first-level regions (states, provinces, cantons...) of a country with their codes" names a specific resource and enumerates the granularity, so there's no ambiguity about what is returned. It also names the downstream consumer (find_city), which distinguishes it from the city-lookup sibling.

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?

"Usable to narrow find_city" gives a concrete when-to-use context that an agent can act on: fetch regions first, then pass a region into the city lookup. There is no explicit when-not guidance or note about what to do without a country code, but the positive routing is clear.

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