Skip to main content
Glama

get_domain_info

Retrieve comprehensive details for any registered domain including status, expiry date, and nameservers to assess domain health and ownership.

Instructions

Get detailed information about a registered domain (status, expiry, nameservers, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesFully qualified domain name (e.g., 'example.com')

Implementation Reference

  • Handler function that calls GET /domains/:domain API and formats domain info (status, expiry, nameservers, owner) as text output.
    export async function getDomainInfo(
      client: BloomfilterClient,
      params: { domain: string },
    ): Promise<McpToolResult> {
      const keyError = client.requiresPrivateKey();
      if (keyError) return keyError;
    
      try {
        await client.ensureAuth();
    
        const { data } = await client.http.get<DomainInfoResponse>(
          `/domains/${encodeURIComponent(params.domain)}`,
          { headers: client.getAuthHeaders() },
        );
    
        const nameservers = data.nameservers?.length ? data.nameservers.join(", ") : "none";
    
        const text = [
          `Domain: ${data.domain}`,
          `Status: ${data.status}`,
          `Created: ${data.registeredAt}`,
          `Expires: ${data.expiresAt}`,
          `Auto-Renew: ${data.autoRenew ? "Yes" : "No"}`,
          `Locked: ${data.locked ? "Yes" : "No"}`,
          `Nameservers: ${nameservers}`,
          `Owner: ${data.walletAddress}`,
        ].join("\n");
    
        return { content: [{ type: "text", text }] };
      } catch (error) {
        return formatToolError(error);
      }
    }
  • Input schema: requires a 'domain' string parameter (the fully qualified domain name).
    params: { domain: string },
  • src/index.ts:108-115 (registration)
    Tool registered with the MCP server under the name 'get_domain_info' with a Zod schema defining the 'domain' parameter.
    server.tool(
      "get_domain_info",
      "Get detailed information about a registered domain (status, expiry, nameservers, etc.).",
      {
        domain: z.string().describe("Fully qualified domain name (e.g., 'example.com')"),
      },
      async (params) => getDomainInfo(client, params),
    );
  • Imports BloomfilterClient, formatToolError, McpToolResult, and DomainInfoResponse types used by the handler.
    import type { BloomfilterClient } from "../client.js";
    import { formatToolError } from "../client.js";
    import type { McpToolResult, DomainInfoResponse } from "../types.js";
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It implies a read-only operation but does not explicitly state safety, error cases, or permissions. The description 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, front-loading the key idea. Every word adds value, with no redundancy. It is efficiently concise.

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 read tool with one parameter and no output schema, the description is brief but covers the essential purpose. However, it lacks details on return format, potential errors, or constraints, making it minimally 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%, with the parameter description already defining the domain format. The tool description adds minimal extra meaning, listing example return fields but not enhancing parameter understanding beyond the schema.

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 action ('Get detailed information') and the resource ('registered domain'), listing specific fields (status, expiry, nameservers). This is unambiguous and distinguishes the tool from siblings like search_domains or register_domain.

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, nor any prerequisites or context. It simply states what the tool does, leaving the agent to infer usage.

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/BloomFilter-Labs/mcp-server-bloomfilter'

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