Skip to main content
Glama

get_country_translations

Retrieve name translations for a country by its UUID, optionally filtered by preferred languages using BCP 47 tags.

Instructions

Get name translations for a country by its UUID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCountry UUID
preferredLanguagesNoComma-separated BCP 47 language tags (e.g. "fr,es,en")

Implementation Reference

  • src/server.ts:143-154 (registration)
    Registration of the 'get_country_translations' tool via server.tool(), including its description and schema definition.
    server.tool(
      'get_country_translations',
      'Get name translations for a country by its UUID.',
      {
        id: z.string().describe('Country UUID'),
        preferredLanguages: z.string().optional().describe('Comma-separated BCP 47 language tags (e.g. "fr,es,en")'),
      },
      async ({ id, preferredLanguages }) => {
        const result = await client.countries.translations(id, { preferredLanguages });
        return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
      },
    );
  • Zod schema for the tool's input: required 'id' (string) and optional 'preferredLanguages' (string).
    {
      id: z.string().describe('Country UUID'),
      preferredLanguages: z.string().optional().describe('Comma-separated BCP 47 language tags (e.g. "fr,es,en")'),
    },
  • Handler function that calls client.countries.translations(id, { preferredLanguages }) and returns the result as JSON text content.
    async ({ id, preferredLanguages }) => {
      const result = await client.countries.translations(id, { preferredLanguages });
      return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
    },
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the operation without mentioning whether it is read-only, idempotent, or what happens on invalid UUIDs.

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?

Single sentence with no extraneous words. Efficiently communicates the core purpose.

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?

Given no output schema and no annotations, the description is adequate for a simple lookup tool but lacks details like return format or error handling. It is minimally viable.

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%, so baseline is 3. The description does not add meaning beyond the schema for either parameter.

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 it retrieves name translations for a country by its UUID. This verb+resource+identifier structure distinguishes it from sibling tools like get_city_translations or get_region_translations.

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 guidance on when to use this tool vs alternatives like get_city_translations. No mention of prerequisites or context where this is appropriate.

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