Skip to main content
Glama

get_city

Retrieve comprehensive city details by providing its UUID. Access name, country, region, and multilingual data.

Instructions

Get full details for a single city by its UUID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCity UUID

Implementation Reference

  • The handler function for the 'get_city' tool. It receives a city UUID, calls client.cities.get(id), and returns the result as formatted JSON text.
    async ({ id }) => {
      const result = await client.cities.get(id);
      return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
    },
  • Input schema for the 'get_city' tool: a single required string parameter 'id' representing the city UUID.
    { id: z.string().describe('City UUID') },
  • src/server.ts:41-49 (registration)
    Registration of the 'get_city' tool via server.tool() with its name, description, input schema, and handler function.
    server.tool(
      'get_city',
      'Get full details for a single city by its UUID.',
      { id: z.string().describe('City UUID') },
      async ({ id }) => {
        const result = await client.cities.get(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 provided; description carries burden. Implies read operation with 'Get', but no disclosure of side effects, idempotency, or rate limits. Adequate for simple lookup 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?

Single sentence of 9 words, front-loaded with purpose, no wasted words.

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?

Tool is simple with 1 param and no output schema. Description states 'full details' but doesn't hint at return fields. Adequate for basic retrieval but could be more complete.

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%; parameter 'id' has description 'City UUID' in schema. Description adds no extra meaning beyond schema. Baseline 3 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?

Description clearly states verb 'Get', resource 'full details for a single city', and input method 'by its UUID'. It distinguishes from sibling tools like search_cities which likely return multiple results.

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. Sibling list provides context but description itself offers no when/when-not or alternative references.

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