whmcs_get_productsRetrieve available products and services from WHMCS, with optional filters for product group, specific product, or server module.
Get available products/services from WHMCS
| Name | Required | Description | Default |
|---|---|---|---|
| gid | No | Filter by product group ID | |
| pid | No | Specific product ID | |
| module | No | Filter by server module |
Changes observed during successful MCP inspections.
v1.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It only states the tool's purpose, omitting critical details such as read-only nature, authentication requirements, pagination, or error handling.
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 redundant information. It is concise, though it could benefit from a slightly more structured format (e.g., listing key parameters).
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 absence of an output schema and only optional parameters, the description does not convey the tool's scope, return format, or how filtering works. The agent lacks sufficient context to interpret results correctly.
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?
All three parameters are fully described in the input schema (100% coverage). The description adds no additional meaning beyond the schema, which is adequate but not enhancing.
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 clear verb ('Get') and resource ('products/services'), making the tool's purpose evident. It is distinguishable from sibling get tools by specifically mentioning products, but lacks explicit differentiation from similar tools like 'whmcs_get_client_products'.
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 is provided on when to use this tool versus alternatives (e.g., whmcs_get_product_groups, whmcs_get_client_products). The agent must rely solely on the name and context, which may lead to incorrect selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.