Skip to main content
Glama

Mark Order as Fraud

whmcs_fraud_order

Mark an order as fraudulent in WHMCS by providing order ID. Optionally cancel associated subscriptions.

Instructions

Mark an order as fraudulent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderidYesOrder ID
cancelsubNoCancel subscription

Implementation Reference

  • src/index.ts:851-867 (registration)
    Registration of the whmcs_fraud_order tool with input schema for orderid and optional cancelsub. The handler calls whmcsClient.fraudOrder() and returns JSON output.
    server.registerTool(
        'whmcs_fraud_order',
        {
            title: 'Mark Order as Fraud',
            description: 'Mark an order as fraudulent',
            inputSchema: {
                orderid: z.number().describe('Order ID'),
                cancelsub: z.boolean().optional().describe('Cancel subscription'),
            },
        },
        async (params) => {
            const result = await whmcsClient.fraudOrder(params);
            return {
                content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
            };
        }
    );
  • Handler method on WhmcsApiClient that calls the WHMCS API action 'FraudOrder' with the orderid and optional cancelsub parameters.
    async fraudOrder(params: {
        orderid: number;
        cancelsub?: boolean;
    }) {
        return this.call<WhmcsApiResponse>('FraudOrder', params);
    }
  • Input schema for whmcs_fraud_order tool: orderid (required number) and cancelsub (optional boolean).
    inputSchema: {
        orderid: z.number().describe('Order ID'),
        cancelsub: z.boolean().optional().describe('Cancel subscription'),
    },
  • Generic call method on WhmcsApiClient that performs the actual HTTP POST request to the WHMCS API. The 'FraudOrder' action is passed through this method.
    async call<T extends WhmcsApiResponse>(action: string, params: Record<string, unknown> = {}): Promise<T> {
        const url = `${this.config.apiUrl.replace(/\/$/, '')}/includes/api.php`;
        
        const postData: Record<string, string> = {
            identifier: this.config.apiIdentifier,
            secret: this.config.apiSecret,
            action: action,
            responsetype: 'json',
            ...this.flattenParams(params)
        };
    
        if (this.config.accessKey) {
            postData.accesskey = this.config.accessKey;
        }
    
        const response = await fetch(url, {
            method: 'POST',
            headers: {
                'Content-Type': 'application/x-www-form-urlencoded',
            },
            body: new URLSearchParams(postData).toString(),
        });
    
        if (!response.ok) {
            throw new Error(`WHMCS API request failed: ${response.status} ${response.statusText}`);
        }
    
        const data = await response.json() as T;
        
        if (data.result === 'error') {
            throw new Error(`WHMCS API error: ${data.message || 'Unknown error'}`);
        }
    
        return data;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose side effects (e.g., impacts on subscriptions, invoices, or client account), reversibility, or authorization requirements.

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

Conciseness4/5

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

Extremely concise at one sentence, front-loads the key action. However, it sacrifices necessary context for brevity.

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?

Even with a simple parameter set and no output schema, the description lacks information about return values, effects on the order, or when to use. It is insufficient for an agent to correctly assess impacts.

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%; parameters have basic descriptions. The tool description adds no extra meaning beyond what the schema already provides, meeting the baseline.

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 'Mark an order as fraudulent' clearly states a specific action (mark) and resource (order) with a distinct status (fraudulent), differentiating it from sibling tools like whmcs_accept_order or whmcs_cancel_order.

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?

No guidance on when to use this tool versus similar order actions (e.g., cancel, pending). It doesn't specify prerequisites like order status or when not to use it, which is important given the numerous sibling tools.

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