Skip to main content
Glama

get_region

Retrieve complete details for a region using its unique UUID. Includes multilingual support for region data.

Instructions

Get full details for a single region by its UUID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesRegion UUID

Implementation Reference

  • Handler for the 'get_region' tool - gets full details for a single region by UUID using client.regions.get(id).
    server.tool(
      'get_region',
      'Get full details for a single region by its UUID.',
      { id: z.string().describe('Region UUID') },
      async ({ id }) => {
        const result = await client.regions.get(id);
        return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
      },
    );
  • Input schema for 'get_region' - requires a single 'id' parameter (string, Region UUID).
    { id: z.string().describe('Region UUID') },
  • src/server.ts:180-188 (registration)
    Tool registration via server.tool() with name 'get_region', description, Zod schema, and handler.
    server.tool(
      'get_region',
      'Get full details for a single region by its UUID.',
      { id: z.string().describe('Region UUID') },
      async ({ id }) => {
        const result = await client.regions.get(id);
        return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
      },
    );
  • Helper: the GeomelonClient instance that provides the regions.get() method used by the handler.
    const client = new GeomelonClient({ apiKey });
Behavior2/5

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

No annotations provided, so the description carries full burden. It only states 'Get' implying a read operation, but lacks details on idempotency, error handling (e.g., 404 if not found), or rate limits.

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?

One sentence, 10 words, front-loaded with the action and resource. No unnecessary information.

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?

For a simple one-parameter tool with no output schema, the description covers the basic purpose but does not elaborate on return format or typical fields, which would help an agent understand what 'full details' means.

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%, and the description repeats the parameter's purpose ('by its UUID') without adding new meaning. Baseline 3 is appropriate as schema already documents the 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?

Clearly states the verb 'Get' and the resource 'full details for a single region', with the key identifier 'by its UUID'. This distinguishes it from sibling tools like list_regions 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 versus alternatives (e.g., list_regions for all regions, get_region_translations for translations). The description does not mention prerequisites or context.

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