Skip to main content
Glama

get_country

Retrieve comprehensive country details using a UUID, including translations and region data.

Instructions

Get full details for a single country by its UUID, including translations and regions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCountry UUID

Implementation Reference

  • The actual handler for the 'get_country' tool. It accepts a single 'id' (country UUID) parameter, calls `client.countries.get(id)` to fetch the full country details, and returns the result as formatted JSON text.
    server.tool(
      'get_country',
      'Get full details for a single country by its UUID, including translations and regions.',
      { id: z.string().describe('Country UUID') },
      async ({ id }) => {
        const result = await client.countries.get(id);
        return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
      },
  • Input schema for 'get_country': a required string 'id' described as 'Country UUID', validated with Zod.
    { id: z.string().describe('Country UUID') },
  • src/server.ts:131-131 (registration)
    Registration via `server.tool()` call inside the `createServer` function. The tool name 'get_country' is registered with a description and handler.
    );
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It indicates what the tool returns (details, translations, regions) but does not disclose potential issues like required permissions, error handling for invalid UUIDs, or whether the call is idempotent. It is adequate but lacks depth.

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 a single sentence that efficiently conveys the tool's purpose and scope without unnecessary words. It is well-structured and front-loaded with the key action.

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?

Given the rich set of sibling tools for specific country attributes, the description clearly positions this as the comprehensive getter. It mentions 'full details' including translations and regions, which covers likely expectations. However, it could be more explicit about the response structure since there is no output schema.

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 description mentions retrieval 'by its UUID', which aligns with the schema parameter 'id' described as 'Country UUID'. Since schema description coverage is 100%, the baseline is 3, and the description adds no additional meaning beyond confirming the parameter's role.

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 tool retrieves full details for a single country by UUID, including translations and regions. It uses a specific verb ('Get') and resource ('country by its UUID'), and the mention of 'full details' distinguishes it from sibling tools that focus on specific aspects like get_country_translations or get_country_regions.

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 the tool is for comprehensive country data retrieval, but it does not explicitly state when to use it versus alternatives like country_overview or the translation-specific tools. There is no guidance on when not to use it or what contexts are inappropriate.

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