Skip to main content
Glama

list_languages

Retrieve a list of languages supported in the Geomelon database. Paginate results with limit and offset parameters.

Instructions

List languages available in the Geomelon database.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset

Implementation Reference

  • The handler function for the 'list_languages' tool. It calls client.languages.list(params) and returns the result as JSON text.
    server.tool(
      'list_languages',
      'List languages available in the Geomelon database.',
      {
        limit: z.number().int().min(1).max(500).optional().describe('Max results'),
        offset: z.number().int().min(0).optional().describe('Pagination offset'),
      },
      async (params) => {
        const result = await client.languages.list(params);
        return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
      },
    );
  • Input schema for the 'list_languages' tool: optional limit (1-500) and offset (>=0) parameters.
    {
      limit: z.number().int().min(1).max(500).optional().describe('Max results'),
      offset: z.number().int().min(0).optional().describe('Pagination offset'),
    },
  • src/server.ts:330-341 (registration)
    Registration of the 'list_languages' tool via server.tool() call, binding the name, description, schema, and handler.
    server.tool(
      'list_languages',
      'List languages available in the Geomelon database.',
      {
        limit: z.number().int().min(1).max(500).optional().describe('Max results'),
        offset: z.number().int().min(0).optional().describe('Pagination offset'),
      },
      async (params) => {
        const result = await client.languages.list(params);
        return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
      },
    );
Behavior2/5

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

No annotations provided, so the description must cover behavior. It only says 'List languages', not mentioning pagination, default ordering, or that it is a read-only operation. Minimal disclosure.

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, clear sentence with no extraneous words. For a simple listing tool, this is appropriately concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lacks details about the return format (e.g., language codes, names) and does not clarify if the entire list or paginated results are returned. Without an output schema, the description should compensate, but it does not.

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% with clear descriptions for limit and offset. The description adds no extra parameter information, which is acceptable as the schema is sufficient.

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 'List languages', specifying the verb and resource. It is distinct from sibling tools like list_countries and list_regions, which have different resources.

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?

No guidance on when to use this tool versus alternatives (e.g., get_language for a specific language). The description implies it is for browsing, but lacks explicit 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