Skip to main content
Glama

get_region_translations

Retrieve region name translations for any region by its UUID. Specify preferred languages using BCP 47 tags to get localized names.

Instructions

Get name translations for a region by its UUID.

Input Schema

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

Implementation Reference

  • src/server.ts:190-201 (registration)
    The tool 'get_region_translations' is registered on the MCP server using server.tool() with its name, description, Zod schema (id + optional preferredLanguages), and handler function.
    server.tool(
      'get_region_translations',
      'Get name translations for a region by its UUID.',
      {
        id: z.string().describe('Region UUID'),
        preferredLanguages: z.string().optional().describe('Comma-separated BCP 47 language tags (e.g. "fr,es,en")'),
      },
      async ({ id, preferredLanguages }) => {
        const result = await client.regions.translations(id, { preferredLanguages });
        return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
      },
    );
  • The handler function for 'get_region_translations' calls client.regions.translations(id, { preferredLanguages }) and returns the result as JSON text content.
      async ({ id, preferredLanguages }) => {
        const result = await client.regions.translations(id, { preferredLanguages });
        return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
      },
    );
  • The input schema defines two parameters: 'id' (required string, Region UUID) and 'preferredLanguages' (optional string, comma-separated BCP 47 language tags).
    {
      id: z.string().describe('Region UUID'),
      preferredLanguages: z.string().optional().describe('Comma-separated BCP 47 language tags (e.g. "fr,es,en")'),
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It hints at a read operation ('Get name translations') but does not mention authentication requirements, rate limits, error handling for invalid UUIDs or missing translations, or side effects. The description is too minimal for a tool without annotations.

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 extremely concise, consisting of a single sentence that conveys the essential purpose without any waste. Every word is necessary and front-loaded.

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 the tool's low complexity (2 parameters, no output schema, no annotations), the description is minimally adequate. However, it fails to explain the behavior when preferredLanguages is omitted, possible return format, or error states. It is sufficient for a straightforward lookup but lacks completeness for robust usage.

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 full coverage (100%) with clear descriptions for both parameters: 'Region UUID' for id and 'Comma-separated BCP 47 language tags...' for preferredLanguages. The description adds no additional meaning beyond the schema, so the baseline score of 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 description clearly states the verb 'Get', the resource 'name translations for a region', and the method 'by its UUID'. It effectively distinguishes from sibling tools like get_city_translations and get_country_translations by specifying 'region'.

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 a region UUID is available and translations are needed, but it does not provide explicit guidance on when to use this tool over alternatives such as get_region (which returns region details) or when not to use it. No exclusions or context are given.

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