whmcs_get_activity_logRetrieve system activity logs from WHMCS with filters for date, user, IP, or description to audit changes and troubleshoot issues.
Get system activity log
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | Filter by date | |
| user | No | Filter by user | |
| userid | No | Filter by user ID | |
| limitnum | No | Number of results | |
| ipaddress | No | Filter by IP address | |
| limitstart | No | Starting offset | |
| description | No | Filter by description |
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 bears full responsibility. It only says 'Get system activity log' without disclosing side effects, permissions needed, or any behavioral traits beyond the implied read-only nature.
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 extremely concise (4 words), which is positive, but it lacks substance and fails to convey important details. It is adequate but not optimally helpful.
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?
With no output schema and many optional filter parameters, the description is insufficient. It does not explain the log contents, filter behavior, or return structure, making the tool incomplete for an agent.
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 description coverage is 100% with all 7 parameters described in the input schema. The tool description does not add any additional meaning beyond what the schema already provides, so it meets the baseline 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?
The description states 'Get system activity log', which is a verb+noun pair indicating the action and resource. However, it does not distinguish this tool from similar siblings like whmcs_get_tickets or whmcs_get_invoices, lacking specificity about what constitutes an 'activity log'.
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?
There is no guidance on when to use this tool versus alternatives. The description merely states the action without any context about appropriate scenarios or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.