Moxie CRM MCP Server

create_ticket_comment

Add a comment to an existing ticket by providing its ID and the comment text. Optionally include an author email for attribution.

Instructions

Add a comment to an existing ticket

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": {
      "ticketId": "<ticketId>",
      "content": "<content>"
    },
    "name": "create_ticket_comment"
  }
}

Input Schema

Name	Required	Description
`content`	Yes	Comment content/text
`ticketId`	Yes	ID of the ticket to comment on
`authorEmail`	No	Email of the comment author

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.2Aug 2, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden. It only states the action 'Add a comment' but does not disclose mutational effects, authentication requirements, failure modes, or response behavior. This is a significant gap for a write operation.

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. It efficiently conveys the core action, though it could be expanded slightly to cover behavioral aspects without losing conciseness.

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

Completeness3/5

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

Given the tool's simplicity and complete schema coverage, the description is minimally adequate. However, the absence of an output schema and annotations means the description should ideally explain return values or side effects, which it does not.

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 all parameters are already described structurally. The description adds no additional semantic context beyond what the schema provides, which is acceptable but not enhanced.

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 uses a specific verb ('Add') and resource ('comment to an existing ticket'), clearly distinguishing it from sibling tools like create_ticket. It precisely communicates the tool's function 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 Guidelines3/5

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

The phrase 'existing ticket' implies the tool should be used for commenting on already-created tickets, providing implicit usage context. However, there is no explicit guidance on when to prefer this over alternatives or any exclusions, though no direct alternative exists among siblings.

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