Starts a ClamAV virus scan on a chosen directory through cPanel to detect malware in hosted files.
Start a ClamAV virus scan on a directory (requires ClamAV plugin on server)
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | Directory path to scan | /home |
Changes observed during successful MCP inspections.
v2.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description only states the action and prerequisite. It does not disclose whether the scan runs asynchronously, how results are returned, whether an existing scan is replaced, or what permissions are required — a significant gap for a side-effect operation.
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, verb-first sentence with no redundant wording. The parenthetical 'requires ClamAV plugin on server' is necessary context and earns its place.
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?
Even though the schema is simple, the lack of annotations and output schema means the description should clarify what happens after starting the scan or how to monitor it (e.g., via get_virus_scan_status). It only mentions the plugin prerequisite, leaving the user to infer next steps.
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%: the 'path' parameter is already described as 'Directory path to scan' with a default of /home. The description adds no parameter-level detail beyond the schema, so the baseline of 3 applies.
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 uses a specific verb ('Start') and resource ('ClamAV virus scan on a directory'), clearly distinguishing it from sibling tools like get_virus_scan_status, list_infected_files, and disinfect_files.
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 description provides a useful prerequisite ('requires ClamAV plugin on server'), which gives clear context, but it does not explicitly state when to use this tool versus alternatives such as get_virus_scan_status or disinfect_files.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.