whmcs_delete_clientDelete a client permanently from WHMCS by providing the client ID. Use when you need to remove a client record and associated data from the system.
Delete a client from WHMCS (use with caution)
| Name | Required | Description | Default |
|---|---|---|---|
| clientid | Yes | The client ID to delete |
Changes observed during successful MCP inspections.
v1.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It only states the action is destructive via 'use with caution', but fails to disclose consequences like irreversibility, cascading effects on orders/invoices, or required admin privileges.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no extraneous words. It efficiently conveys the core purpose and a warning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a destructive tool with no output schema and no annotations, the description is too sparse. It should explain what happens to associated data (e.g., orders, invoices) whether the action is reversible, and any permission requirements.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and the parameter 'clientid' is described in the schema. The description adds no additional meaning beyond what the schema already provides, so it meets the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Delete a client from WHMCS' clearly states the action (delete) and the resource (client), distinguishing it from sibling tools like add, update, or get client operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The only guideline is 'use with caution', which is vague. No explicit when-to-use, when-not-to-use, or alternatives are provided. An agent would not know if deletion requires specific permissions or has prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.