whmcs_get_todo_itemsRetrieve WHMCS admin to-do items. Use optional status, result limit, and offset filters to get the exact task list you need.
Get admin to-do items
| Name | Required | Description | Default |
|---|---|---|---|
| status | No | Filter by status | |
| limitnum | No | Number of results | |
| limitstart | No | Starting offset |
Changes observed during successful MCP inspections.
v1.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. It does not disclose behavioral traits like whether this is a read-only operation, if authentication or admin rights are required, or what side effects occur. A simple 'Get' implies read, but it should be explicit.
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 (one sentence) and front-loaded, but it sacrifices necessary detail. It omits information about output, pagination, or filtering behavior that would be helpful. While not verbose, it is under-specified for a production tool.
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?
Given the lack of output schema and annotations, the description should provide more context. It does not explain the return format, pagination behavior (though parameters hint at limits), or any authorization requirements. The tool is simple but the description is insufficient for effective use.
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?
The input schema provides descriptions for all three parameters (limitstart, limitnum, status) with enum for status. With 100% schema coverage, the description adds no additional meaning beyond what the schema already states. Baseline 3 is appropriate.
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 'Get admin to-do items' clearly specifies the action (Get) and the resource (admin to-do items). It distinguishes from sibling tools like whmcs_get_tickets or whmcs_get_activity_log by indicating a focus on to-do items. However, it could be more specific about the scope (e.g., 'list all' or 'retrieve filtered list').
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 usage guidance is provided. The description does not indicate when to use this tool over alternatives, such as other get_* tools for admin tasks, nor does it mention any prerequisites or context for use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.