Skip to main content
Glama

Comment support ticket

comment_support_ticket
Destructive

Legacy Platform support desk only. For new requests and support.ankra.app conversations use support_create_ticket, support_list_tickets, support_get_ticket and support_reply. Reply on an existing support ticket on the user's behalf - answer a question Ankra support asked, add evidence, or report that the problem changed. The reply reaches the support team; a ticket waiting on the customer moves back to in progress. Identify the ticket by ticket_number or ticket_id. To close a ticket the user considers resolved, use close_support_ticket instead.

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": {
      "body": "<body>"
    },
    "name": "comment_support_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesThe reply (markdown, at most 10000 characters).
ticket_idNoThe support ticket UUID. Optional when ticket_number is given.
ticket_numberNoThe per-organisation support ticket number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing the concrete side effect: the reply reaches the support team and a ticket waiting on the customer moves back to in progress — a state transition an agent could not infer from readOnlyHint=false/destructiveHint=true alone. It stops short of covering permissions, whether the comment is editable/retractable, or error behavior, and the destructiveHint=true annotation is never reconciled with what reads like an additive comment 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?

Front-loaded with the scope restriction and the primary action before the routing list, and every sentence carries routing or behavior information. The four-sibling enumeration in the first sentence is slightly dense but earns its place as the legacy-vs-new discriminator.

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?

For a 3-parameter, fully documented, mutation-style tool with no output schema, the definition covers scope, alternatives, side effects, and ticket identification. Remaining gaps are the destructiveHint inconsistency and lack of any note on what a successful reply returns or requires in terms of access.

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 the schema already documents body (markdown, 10000 max), ticket_id, and ticket_number, including that ticket_id is optional when ticket_number is supplied. The description restates the either/or identification rule without adding format, precedence, or validation guidance beyond the schema, so baseline 3 applies.

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?

Specific verb + resource: "Reply on an existing support ticket on the user's behalf", with explicit examples of reply content (answer a question, add evidence, report a changed problem). It also draws a hard scope boundary — "Legacy Platform support desk only" — distinguishing it from the support_* family used for new requests.

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

Usage Guidelines5/5

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

Explicit when-to-use (reply to an existing ticket), when-not (new requests and support.ankra.app conversations go to support_create_ticket / support_list_tickets / support_get_ticket / support_reply), and a named alternative for a closely related action (close_support_ticket for resolved tickets). Nothing is left to inference about tool selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.