Skip to main content
Glama

get_city_translations

Retrieve all name translations for a city by providing its UUID. Get multilingual city names from the Geomelon dataset.

Instructions

Get all available name translations for a city by its UUID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCity UUID

Implementation Reference

  • The `get_city_translations` tool handler: registered via `server.tool()`, takes a city UUID (`id: z.string()`) and calls `client.cities.translations(id)` to get all available name translations for a city, returning the result as JSON text.
    server.tool(
      'get_city_translations',
      'Get all available name translations for a city by its UUID.',
      { id: z.string().describe('City UUID') },
      async ({ id }) => {
        const result = await client.cities.translations(id);
        return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
      },
    );
  • src/server.ts:51-54 (registration)
    Registration of the `get_city_translations` tool using `server.tool()` with the name 'get_city_translations' and a description.
    server.tool(
      'get_city_translations',
      'Get all available name translations for a city by its UUID.',
      { id: z.string().describe('City UUID') },
  • Input schema for `get_city_translations`: expects `id` (string, UUID) describing 'City UUID'.
    { id: z.string().describe('City UUID') },
Behavior3/5

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

No annotations are provided, so the description carries full burden. It indicates a read operation, but lacks details on side effects, authentication, error handling, or output format. It is adequate but minimal.

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?

A single, clear sentence with no redundant words. Front-loaded with the action and resource.

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, single-parameter read tool, the description is adequate. It explains the purpose and input. Could mention expected output or constraints, but not necessary given low complexity.

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 has 100% coverage with description 'City UUID' for the parameter. The description does not add additional semantic meaning beyond what the schema already provides.

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 ('all available name translations for a city'), and the parameter ('by its UUID'). It distinguishes from siblings like get_city (which returns city details) and city_context.

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 when to use (when you need translations) but does not explicitly state when not to use it or mention alternatives. No exclusions or context provided beyond the basic purpose.

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