simple-support-system-mcp

Overview Schema Source Related Servers Discussions Admin

Reply to ticket

reply_to_ticket

Post a reply as a comment on a support ticket, triggering notification emails to the requester. Include an email when unauthenticated; comments may await moderation.

Instructions

Post a reply as a comment on a ticket. This is the normal way to answer a ticket. The reply triggers the notification mails of the package. Without an API key and without a logged in session the email field is required, and moderation may hold the comment back until it is approved.

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>",
      "comment": "<comment>"
    },
    "name": "reply_to_ticket"
  }
}

Input Schema

Name	Required	Description
`email`	No	Author email, required for unauthenticated calls.
`token`	No	Access token of a private project. Only needed without an API key, or for projects behind a private link.
`comment`	Yes	Text of the reply.
`ticketId`	Yes	Ticket the reply belongs to.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4Oct 19, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations only carry openWorldHint=true, so the description bears the full behavioral burden and delivers: it discloses the notification-email side effect, the unauthenticated email requirement, and that moderation may withhold the comment pending approval. These are exactly the non-obvious traits an agent cannot get from the schema or annotations.

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?

Four short sentences, front-loaded with the action and the primary-use statement, with no filler. The auth sentence partially duplicates the schema's email description, which is the only small redundancy.

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

Completeness4/5

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

With no output schema and minimal annotations, the description adequately covers auth paths, side effects, and moderation gating for a create-comment tool. It does not say what is returned (comment id) or how failures surface, which leaves a modest gap.

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 all four parameters are already documented (email 'required for unauthenticated calls', token for private projects). The description restates the email/auth condition with added moderation context but says nothing about token or the comment/ticketId fields, so baseline 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?

States a specific verb and resource ('Post a reply as a comment on a ticket') and frames the role as the primary answer path. It does not name or contrast with nearby siblings such as update_comment or approve_comment, so an agent still has to infer the boundary from the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

'This is the normal way to answer a ticket' gives an explicit default-use signal, which is stronger than implied guidance. There are no when-not conditions or named alternatives (e.g. when to use update_comment instead), so it stops short of full routing guidance.

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