Skip to main content
Glama

Get Domain Lock Status

whmcs_get_domain_lock_status

Retrieves the current lock or unlock status for a domain using its ID. Helps determine if a domain is protected against unauthorized transfers.

Instructions

Get lock/unlock status for a domain

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainidYesDomain ID

Implementation Reference

  • src/index.ts:715-730 (registration)
    Registration of the 'whmcs_get_domain_lock_status' tool with MCP server, defining its name, description, input schema (domainid), and handler that delegates to whmcsClient.getDomainLockingStatus()
    server.registerTool(
        'whmcs_get_domain_lock_status',
        {
            title: 'Get Domain Lock Status',
            description: 'Get lock/unlock status for a domain',
            inputSchema: {
                domainid: z.number().describe('Domain ID'),
            },
        },
        async (params) => {
            const result = await whmcsClient.getDomainLockingStatus(params);
            return {
                content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
            };
        }
    );
  • Input schema for the tool: expects a single required 'domainid' parameter of type number
        inputSchema: {
            domainid: z.number().describe('Domain ID'),
        },
    },
  • The actual handler/helper method on WhmcsApiClient that calls the WHMCS API action 'DomainGetLockingStatus' with the given domainid, returning a response containing lockstatus string
    async getDomainLockingStatus(params: { domainid: number }) {
        return this.call<WhmcsApiResponse & { lockstatus: string }>('DomainGetLockingStatus', params);
    }
  • The underlying API client 'call' method that all tools use to make HTTP POST requests to the WHMCS API endpoint
    async call<T extends WhmcsApiResponse>(action: string, params: Record<string, unknown> = {}): Promise<T> {
        const url = `${this.config.apiUrl.replace(/\/$/, '')}/includes/api.php`;
        
        const postData: Record<string, string> = {
            identifier: this.config.apiIdentifier,
            secret: this.config.apiSecret,
            action: action,
            responsetype: 'json',
            ...this.flattenParams(params)
        };
    
        if (this.config.accessKey) {
            postData.accesskey = this.config.accessKey;
        }
    
        const response = await fetch(url, {
            method: 'POST',
            headers: {
                'Content-Type': 'application/x-www-form-urlencoded',
            },
            body: new URLSearchParams(postData).toString(),
        });
    
        if (!response.ok) {
            throw new Error(`WHMCS API request failed: ${response.status} ${response.statusText}`);
        }
    
        const data = await response.json() as T;
        
        if (data.result === 'error') {
            throw new Error(`WHMCS API error: ${data.message || 'Unknown error'}`);
        }
    
        return data;
    }
  • Related helper: updateDomainLockingStatus method that calls the sibling WHMCS API action for updating domain lock status
    async updateDomainLockingStatus(params: {
        domainid: number;
        lockstatus?: boolean;
    }) {
        return this.call<WhmcsApiResponse>('DomainUpdateLockingStatus', params);
    }
Behavior2/5

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

No annotations provided, so the description must convey behavioral traits. It indicates a read operation ('get') but lacks details on safety (e.g., idempotent), error handling if domain ID is invalid, or permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (9 words), making it concise. It front-loads the action and resource, but could include a bit more context without becoming verbose.

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 the tool has no output schema, the description should hint at the return format (e.g., returns 'locked' or 'unlocked' string). It does not, leaving the agent to guess. Also lacks explanation of input validation or default behavior.

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 parameter description 'Domain ID'. The tool description adds no extra meaning beyond the schema. Baseline score of 3 applies as the schema already documents the parameter well enough.

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 the lock/unlock status for a domain, using a specific verb and resource. It distinguishes itself from the sibling 'whmcs_update_domain_lock_status' which sets the status.

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 gives no explicit guidance on when to use this tool versus alternatives. It implies use for checking status, but does not mention prerequisites (e.g., domain must exist) or scenarios like checking before updating.

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/scarecr0w12/whmcs-mcp-tool'

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