whmcs_accept_quoteAccept a quote by ID and convert it to an invoice. Turn approved quotes into billable invoices without manual data entry.
Accept a quote and convert to invoice
| Name | Required | Description | Default |
|---|---|---|---|
| quoteid | Yes | Quote ID |
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 must carry full burden. It only states the action without disclosing side effects (e.g., quote status change, irreversibility), authorization needs, or other behavioral traits beyond the basic mutation.
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 sentence with 5 words, highly concise and front-loaded. Every word is earned, but could be slightly expanded without losing conciseness.
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 tool's simplicity (1 param, no output schema, no annotations), the description is minimally complete but lacks behavioral context and usage cues. It barely meets the minimum viable threshold.
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% (1 param with description 'Quote ID'). The description adds no additional meaning beyond the schema, so 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 clearly states the verb 'Accept' and the resource 'quote', and specifies the outcome 'convert to invoice', distinguishing it from sibling tools like whmcs_create_quote and whmcs_create_invoice.
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 implies use after a quote is created, but gives no explicit guidance on when to use this tool vs alternatives like whmcs_create_invoice or whmcs_create_quote. No exclusions or prerequisites are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.