Skip to main content
Glama

Add Payment

whmcs_add_payment

Record a payment on a WHMCS invoice by providing invoice ID, transaction ID, and gateway. Optionally specify amount, fees, payment date, and suppress email notifications.

Instructions

Record a payment on an invoice

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
invoiceidYesInvoice ID
transidYesTransaction ID
gatewayYesPayment gateway name
amountNoPayment amount
feesNoTransaction fees
noemailNoDo not send email
dateNoPayment date (YYYY-MM-DD)

Implementation Reference

  • src/index.ts:349-370 (registration)
    Registration of the 'whmcs_add_payment' tool with the MCP server. Defines input schema using Zod for invoiceid (required), transid (required), gateway (required), and optional amount, fees, noemail, date. The handler delegates to whmcsClient.addPayment().
    server.registerTool(
        'whmcs_add_payment',
        {
            title: 'Add Payment',
            description: 'Record a payment on an invoice',
            inputSchema: {
                invoiceid: z.number().describe('Invoice ID'),
                transid: z.string().describe('Transaction ID'),
                gateway: z.string().describe('Payment gateway name'),
                amount: z.number().optional().describe('Payment amount'),
                fees: z.number().optional().describe('Transaction fees'),
                noemail: z.boolean().optional().describe('Do not send email'),
                date: z.string().optional().describe('Payment date (YYYY-MM-DD)'),
            },
        },
        async (params) => {
            const result = await whmcsClient.addPayment(params);
            return {
                content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
            };
        }
    );
  • The inline handler function for the whmcs_add_payment tool. It calls whmcsClient.addPayment(params) and returns the result as JSON text content.
    async (params) => {
        const result = await whmcsClient.addPayment(params);
        return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
        };
    }
  • The addPayment method in the WhmcsApiClient class. Sends an 'AddInvoicePayment' API action to WHMCS with parameters: invoiceid, transid, gateway, amount, fees, noemail, date. This is the actual implementation that calls the WHMCS API.
    async addPayment(params: {
        invoiceid: number;
        transid: string;
        gateway: string;
        amount?: number;
        fees?: number;
        noemail?: boolean;
        date?: string;
    }) {
        return this.call<WhmcsApiResponse>('AddInvoicePayment', params);
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden but only states the action. It does not disclose side effects (e.g., invoice status changes), permissions, or idempotency, leaving significant behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only one sentence, which is under-specified for a tool with 7 parameters. While concise, it sacrifices important detail, making it less useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and 7 parameters, the description lacks essential context such as return values, invoice status effects, or prerequisites, resulting in incomplete guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds no parameter-specific meaning beyond the schema, offering minimal added value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Record a payment on an invoice' clearly states the verb (record) and the resource (payment on an invoice), distinguishing it from siblings like whmcs_apply_credit or 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.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool vs alternatives, such as whether to use it when an invoice is open or how it relates to other payment actions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/scarecr0w12/whmcs-mcp-tool'

If you have feedback or need assistance with the MCP directory API, please join our Discord server