Skip to main content
Glama

Update Domain Lock Status

whmcs_update_domain_lock_status

Lock or unlock a domain by providing its ID and a boolean lock status. This controls transfer protection.

Instructions

Lock or unlock a domain

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainidYesDomain ID
lockstatusNoLock status (true to lock)

Implementation Reference

  • src/index.ts:732-748 (registration)
    Registration of the 'whmcs_update_domain_lock_status' tool with MCP server. Defines input schema (domainid required, lockstatus optional boolean) and delegates to whmcsClient.updateDomainLockingStatus().
    server.registerTool(
        'whmcs_update_domain_lock_status',
        {
            title: 'Update Domain Lock Status',
            description: 'Lock or unlock a domain',
            inputSchema: {
                domainid: z.number().describe('Domain ID'),
                lockstatus: z.boolean().optional().describe('Lock status (true to lock)'),
            },
        },
        async (params) => {
            const result = await whmcsClient.updateDomainLockingStatus(params);
            return {
                content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
            };
        }
    );
  • Input schema for the tool: domainid (number, required) and lockstatus (boolean, optional).
    inputSchema: {
        domainid: z.number().describe('Domain ID'),
        lockstatus: z.boolean().optional().describe('Lock status (true to lock)'),
    },
  • Handler function that calls whmcsClient.updateDomainLockingStatus(params) and returns the JSON-stringified result.
    async (params) => {
        const result = await whmcsClient.updateDomainLockingStatus(params);
        return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
        };
    }
  • The WhmcsApiClient.updateDomainLockingStatus() helper method that calls the WHMCS API action 'DomainUpdateLockingStatus' with the provided params.
     * Update 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 are provided, so the description must disclose behavioral traits. It only states the action but does not explain whether the change is immediate, requires permissions, or any side effects. The description is minimal for a mutation tool.

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 is front-loaded and contains no unnecessary words. It is appropriately sized for the tool's simplicity.

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 lack of annotations and output schema, the description should provide more context about the effect of omitting the optional lockstatus parameter, the return value, and any confirmation. It is incomplete for a mutation tool.

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 covers 100% of parameters with descriptions. The description adds no extra meaning beyond what the schema provides, so it meets the baseline but does not enhance understanding.

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 'Lock or unlock a domain' clearly states the verb and resource, distinguishing it from the sibling tool whmcs_get_domain_lock_status which reads status. However, it could be more precise by indicating it sets the lock status to the provided boolean.

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?

No guidance is provided on when to use this tool versus alternatives like whmcs_get_domain_lock_status or other update tools. There is no mention of prerequisites, when not to use it, or recommended 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/scarecr0w12/whmcs-mcp-tool'

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