Skip to main content
Glama

get_country_regions

Retrieve all administrative regions of a country using its UUID. Input a country UUID to get a list of its regions.

Instructions

Get all administrative regions belonging to a country by its UUID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCountry UUID

Implementation Reference

  • src/server.ts:156-164 (registration)
    Registration of the 'get_country_regions' tool using server.tool(). The handler calls client.countries.regions(id) and returns the result as formatted JSON text. Input schema expects a single 'id' (Country UUID) string.
    server.tool(
      'get_country_regions',
      'Get all administrative regions belonging to a country by its UUID.',
      { id: z.string().describe('Country UUID') },
      async ({ id }) => {
        const result = await client.countries.regions(id);
        return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
      },
    );
  • Input schema for 'get_country_regions': requires a string field 'id' described as 'Country UUID'. Uses Zod for validation.
    { id: z.string().describe('Country UUID') },
  • Handler function for 'get_country_regions'. It extracts 'id' from the input, calls client.countries.regions(id) to fetch administrative regions for the given country UUID, and returns the result as a JSON-formatted text content.
    async ({ id }) => {
      const result = await client.countries.regions(id);
      return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
    },
Behavior3/5

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

No annotations exist, so the description must cover behavioral traits. While it accurately describes the retrieval, it does not mention any details about ordering, limits, or default behavior beyond the obvious.

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?

The description is a single, front-loaded sentence with no unnecessary words. Every word earns its place.

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

Completeness5/5

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

Given the tool's simplicity (single parameter, no output schema), the description adequately covers the needed context: what is retrieved and the identifying attribute.

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?

The input schema already provides a description 'Country UUID' for the single parameter 'id'. The description repeats this without adding new meaning, and schema coverage is 100%, so baseline 3 applies.

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 description clearly states the action 'Get', the resource 'administrative regions', and the filter 'by country UUID'. It distinguishes from sibling tools like 'get_region' (single region) and 'list_regions' (all regions).

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?

The description implies usage when you have a country UUID and need its administrative regions, but it does not explicitly compare with alternatives like 'list_regions' or state when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/930m310n/geomelon-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server