Skip to main content
Glama

Get Quotes

whmcs_get_quotes

Retrieve a list of quotes from your WHMCS installation with optional filters for specific client, subject, or stage.

Instructions

Get list of quotes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitstartNoStarting offset
limitnumNoNumber of results
quoteidNoSpecific quote ID
useridNoFilter by client ID
subjectNoFilter by subject
stageNoFilter by stage

Implementation Reference

  • src/index.ts:1225-1245 (registration)
    Registration of the 'whmcs_get_quotes' tool with the MCP server, defining its input schema and delegating to whmcsClient.getQuotes().
    server.registerTool(
        'whmcs_get_quotes',
        {
            title: 'Get Quotes',
            description: 'Get list of quotes',
            inputSchema: {
                limitstart: z.number().optional().describe('Starting offset'),
                limitnum: z.number().optional().describe('Number of results'),
                quoteid: z.number().optional().describe('Specific quote ID'),
                userid: z.number().optional().describe('Filter by client ID'),
                subject: z.string().optional().describe('Filter by subject'),
                stage: z.string().optional().describe('Filter by stage'),
            },
        },
        async (params) => {
            const result = await whmcsClient.getQuotes(params);
            return {
                content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
            };
        }
    );
  • Handler function that executes when the 'whmcs_get_quotes' tool is called; invokes whmcsClient.getQuotes() and returns the result.
    async (params) => {
        const result = await whmcsClient.getQuotes(params);
        return {
            content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
        };
    }
  • Input schema for whmcs_get_quotes defining optional parameters: limitstart, limitnum, quoteid, userid, subject, and stage.
        limitstart: z.number().optional().describe('Starting offset'),
        limitnum: z.number().optional().describe('Number of results'),
        quoteid: z.number().optional().describe('Specific quote ID'),
        userid: z.number().optional().describe('Filter by client ID'),
        subject: z.string().optional().describe('Filter by subject'),
        stage: z.string().optional().describe('Filter by stage'),
    },
  • The getQuotes() method on the WhmcsApiClient class that calls the WHMCS API 'GetQuotes' action and returns typed response data.
    async getQuotes(params: {
        limitstart?: number;
        limitnum?: number;
        quoteid?: number;
        userid?: number;
        subject?: string;
        stage?: string;
        datecreated?: string;
        lastmodified?: string;
        validuntil?: string;
    } = {}) {
        return this.call<WhmcsApiResponse & {
            totalresults: number;
            startnumber: number;
            numreturned: number;
            quotes: { quote: Array<{
                id: number;
                subject: string;
                stage: string;
                validuntil: string;
                userid: number;
                firstname: string;
                lastname: string;
                companyname: string;
                email: string;
                datecreated: string;
                lastmodified: string;
                datesent: string;
                dateaccepted: string;
                total: string;
            }> };
        }>('GetQuotes', params);
    }
Behavior2/5

Does 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.

Conciseness3/5

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.

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 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.

Parameters3/5

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.

Purpose4/5

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.

Usage Guidelines2/5

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.

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