whmcs_get_quotesFetch WHMCS quotes filtered by stage, client, ID, or subject, with pagination support. Use to access quote records for billing or reporting.
Get list of quotes
| Name | Required | Description | Default |
|---|---|---|---|
| stage | No | Filter by stage | |
| userid | No | Filter by client ID | |
| quoteid | No | Specific quote ID | |
| subject | No | Filter by subject | |
| 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?
Without annotations, the description carries full burden, but it only says 'Get list of quotes'. It does not disclose read-only nature, pagination behavior, performance characteristics, or any side effects.
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 very short (4 words) but sacrifices necessary context for brevity. It is front-loaded but does not fully earn its place as it omits helpful details.
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 no output schema and 6 optional parameters, the description is too minimal. It fails to explain expected output, filter usage, or relationship to sibling tools like whmcs_get_quote.
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 provides full descriptions for all 6 parameters (100% coverage). The description adds no additional meaning beyond the schema, so baseline score of 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 list of quotes' clearly states the action (Get) and resource (list of quotes), distinguishing it from other WHMCS tools like whmcs_get_invoices. However, it lacks specificity about filtering or scope.
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 related siblings such as whmcs_get_quote (singular) or whmcs_create_quote. The agent receives no context for decision-making.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.