Skip to main content
Glama

Module Suspend

whmcs_module_suspend

Suspend a WHMCS service account by providing the service ID. Optionally include a suspension reason.

Instructions

Suspend a service account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountidYesService ID
suspendreasonNoSuspension reason

Implementation Reference

  • src/index.ts:928-944 (registration)
    Registration of the 'whmcs_module_suspend' tool with the MCP server. Defines its title, description, and inputSchema (accountid required, suspendreason optional). The handler delegates to whmcsClient.moduleSuspend().
    server.registerTool(
        'whmcs_module_suspend',
        {
            title: 'Module Suspend',
            description: 'Suspend a service account',
            inputSchema: {
                accountid: z.number().describe('Service ID'),
                suspendreason: z.string().optional().describe('Suspension reason'),
            },
        },
        async (params) => {
            const result = await whmcsClient.moduleSuspend(params);
            return {
                content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
            };
        }
    );
  • Implementation of the moduleSuspend method in WhmcsApiClient. Accepts accountid and optional suspendreason, then calls the WHMCS API action 'ModuleSuspend'.
    async moduleSuspend(params: {
        accountid: number;
        suspendreason?: string;
    }) {
        return this.call<WhmcsApiResponse>('ModuleSuspend', params);
    }
  • Zod schema defining the input parameters for whmcs_module_suspend: accountid (required number) and suspendreason (optional string).
    inputSchema: {
        accountid: z.number().describe('Service ID'),
        suspendreason: z.string().optional().describe('Suspension reason'),
    },
Behavior2/5

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

With no annotations, the description should disclose behavioral aspects. It does not mention side effects, reversibility, or required permissions. The single sentence only states the basic action.

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 concise with a single sentence. No unnecessary words, but it could arguably be slightly more informative without sacrificing brevity.

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 output schema and many sibling tools, the description is insufficient. It lacks information about return values, side effects, or how it fits into the module lifecycle.

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 description coverage is 100% with clear parameter descriptions. The tool description adds no further semantic value beyond what the schema provides, meriting the baseline score.

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 'Suspend a service account' clearly states the action and the resource, using a specific verb. It distinguishes the tool's purpose from read-only tools, but does not explicitly differentiate from sibling tools like whmcs_module_unsuspend.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives (e.g., terminate or unsuspend), nor does it mention prerequisites or 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