whmcs_get_client_detailsFetches full client details from WHMCS using client ID or email, with option to include statistics for account insights.
Get detailed information about a specific client
| Name | Required | Description | Default |
|---|---|---|---|
| No | The email address to search for | ||
| stats | No | Include client statistics | |
| clientid | No | The client ID to retrieve |
Changes observed during successful MCP inspections.
v1.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description does not disclose read-only nature, required permissions, or what constitutes 'detailed information'. Agents have no behavioral clues beyond the vague description.
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?
Single sentence of 9 words, no redundancy. Front-loads the purpose with no wasted text. Highly concise.
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?
No output schema, no description of return values or side effects. For a data retrieval tool, the description should at least hint at the output structure or scoping, which is missing.
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?
Input schema covers all 3 parameters with descriptions (100% coverage). Description adds no additional meaning beyond schema, warranting baseline score of 3.
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?
Description clearly states verb 'get' and resource 'detailed information about a specific client'. It is specific but does not differentiate from sibling 'whmcs_get_clients' which also retrieves client data.
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?
No guidance on when to use this tool vs alternatives like whmcs_get_clients or whmcs_get_client_products. Lacks context on prerequisites or typical use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.