Skip to main content
Glama
cfenzo
by cfenzo

list_tlds

Lists available top-level domain categories and their contents to help users explore TLD options for domain registration.

Instructions

List available TLD categories and their contents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoCategory to list. Default: all

Implementation Reference

  • The handler function that executes the list_tlds tool logic, accepting a category argument and returning the appropriate TLD lists (general, tech, country, or all).
    case "list_tlds": {
      const category = (args?.category as string) || "all";
      let result: Record<string, string[]>;
    
      switch (category) {
        case "general":
          result = { general: POPULAR_TLDS };
          break;
        case "tech":
          result = { tech: TECH_TLDS };
          break;
        case "country":
          result = { country: COUNTRY_TLDS };
          break;
        case "all":
        default:
          result = {
            general: POPULAR_TLDS,
            tech: TECH_TLDS,
            country: COUNTRY_TLDS,
          };
      }
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • The tool schema definition that defines the input parameters for list_tlds, including the category enum (general, tech, country, all).
    {
      name: "list_tlds",
      description: "List available TLD categories and their contents.",
      inputSchema: {
        type: "object" as const,
        properties: {
          category: {
            type: "string",
            enum: ["general", "tech", "country", "all"],
            description: "Category to list. Default: all",
          },
        },
      },
    },
  • General TLD list constant used by list_tlds handler for the 'general' category.
    export const POPULAR_TLDS = [
      "com",
      "net",
      "org",
      "io",
      "co",
      "dev",
      "app",
      "ai",
      "xyz",
      "me",
      "info",
      "biz",
      "tech",
      "online",
      "site",
      "cloud",
    ];
  • Country-code TLD list constant used by list_tlds handler for the 'country' category.
    export const COUNTRY_TLDS = [
      "uk",
      "de",
      "fr",
      "nl",
      "es",
      "it",
      "pl",
      "ru",
      "jp",
      "cn",
      "au",
      "ca",
      "us",
      "in",
      "br",
    ];
  • Tech-focused TLD list constant used by list_tlds handler for the 'tech' category.
    export const TECH_TLDS = [
      "io",
      "dev",
      "app",
      "ai",
      "tech",
      "cloud",
      "software",
      "systems",
      "digital",
      "code",
    ];
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it lists categories and contents. It doesn't disclose behavioral traits like whether it's read-only, requires authentication, has rate limits, or what format the output takes (e.g., list, structured data). This leaves significant gaps for a tool with potential complexity.

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, efficient sentence that directly states the tool's function without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what 'contents' means (e.g., TLD names, descriptions, counts) or the return format, leaving the agent unsure about the tool's behavior and output, which is inadequate for a tool that might return complex data.

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, fully documenting the 'category' parameter with enum values and default. The description adds no additional meaning beyond implying categories exist, so it meets the baseline of 3 where the schema does the heavy lifting without compensating for gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('List') and the resource ('available TLD categories and their contents'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'check_alternative_tlds' or 'suggest_domains', which also involve TLDs/domains, so it misses full sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives like 'check_domain' or 'suggest_domains'. It lacks context about scenarios where listing TLD categories is appropriate, such as for domain selection or research, leaving usage unclear.

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/cfenzo/domain-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server