Skip to main content
Glama
Yadley

WHMCS MCP Server

by Yadley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Open Ticket

whmcs_open_ticket

Create a new support ticket in WHMCS with department, subject, and message. Specify client, priority, or related service to route the request correctly.

Instructions

Create a new support ticket

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName (if not a client)
adminNoOpened by admin
emailNoEmail (if not a client)
deptidYesDepartment ID
messageYesTicket message/description
subjectYesTicket subject
clientidNoClient ID
domainidNoRelated domain ID
markdownNoMessage contains markdown
priorityNoTicket priority
contactidNoContact ID
serviceidNoRelated service ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits but only states creation. Missing details on side effects, permissions, or return values.

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

Conciseness5/5

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

One direct sentence with no unnecessary words; front-loaded and concise.

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 12 parameters, no output schema, and no annotations, the description lacks completeness about behavior, return format, and prerequisites.

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%, baseline 3. The description adds no additional parameter information beyond what the schema provides.

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 'Create a new support ticket' clearly states the action and resource, distinguishing it from sibling tools like replies and notes.

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 alternatives; e.g., missing comparisons to whmcs_add_ticket_note or whmcs_add_ticket_reply.

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

Deploy Server

Other Tools