Moxie CRM MCP Server

create_ticket

Create a new support ticket in your workspace with a known contact email, ticket type, and comment. Optionally include due date, subject, or structured Q&A for more context.

Instructions

Create a new support ticket in your workspace

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "userEmail": "<userEmail>",
      "ticketType": "<ticketType>",
      "comment": "<comment>"
    },
    "name": "create_ticket"
  }
}

Input Schema

Name	Required	Description
`comment`	Yes	Required - The initial details/comment of the ticket
`dueDate`	No	Due date in ISO format (YYYY-MM-DD)
`subject`	No	The ticket subject/title
`formData`	No	Additional structured questions/answers that can be mapped to ticket data
`userEmail`	Yes	Required - Email of a known contact in your workspace. The ticket will be rejected if the email is not found
`ticketType`	Yes	Required - The string value of the ticket type which can be found in Tickets >> Settings

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.2Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that a ticket is created, omitting important behavior such as userEmail validation ('ticket will be rejected if the email is not found'), ticket type requirements, or what happens on success/failure. This is a significant transparency gap for a creation tool.

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?

The description is a single, front-loaded sentence with no wasted words. While it is minimal, conciseness is a strength here; the lack of detail does not inflate the score but the structure is efficient.

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?

For a tool with six parameters, a nested object, and no output schema, the one-sentence description provides very little beyond the schema itself. It does not explain required inputs, rejection behavior, or the tool's relationship to related sibling tools, leaving the description incomplete for effective tool selection and invocation.

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 description coverage is 100%, so the schema already thoroughly documents all six parameters including required fields and nested formData. The description adds no parameter-level meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 in your workspace' uses a specific verb and resource, clearly distinguishing this tool from siblings like create_ticket_comment and create_form_submission. The workspace scoping adds context without ambiguity.

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 about when to use this tool versus alternatives such as create_ticket_comment or how to handle prerequisites like using a known contact email. The description does not mention exclusions or scenarios where another tool would be more appropriate.

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