Skip to main content
Glama

Ticket comment

ticket_comment
Destructive

Post a comment on an AI work board ticket. Use this to record findings, evidence, questions for colleagues (agents or humans), and progress updates - the ticket timeline is the team's shared paper trail. Identify the ticket by ticket_number or ticket_id.

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": "ticket_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesThe comment body (markdown).
ticket_idNoThe ticket UUID. Optional when ticket_number is given.
ticket_numberNoThe per-organisation ticket number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=true, so the write-and-non-idempotent profile is known. The description adds genuinely useful context by framing the comment as visible to the whole team ("shared paper trail"), but it never explains the destructiveHint=true flag - nothing about whether comments can be edited or removed, or whether posting notifies anyone. That unexplained destructiveness is a real gap given the 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?

Three sentences, front-loaded with the action, then purpose, then identification. No filler; the only mild redundancy is the ticket-identification sentence repeating the schema.

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 simple three-parameter tool with no output schema, the description covers what it does, why an agent would use it, and how to target the ticket. The remaining omission is the return value and the consequences of the destructiveHint=true flag, which are minor but not nothing.

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 baseline applies. The sentence "Identify the ticket by ticket_number or ticket_id" restates what the schema already encodes (ticket_id is "Optional when ticket_number is given") and adds no format or precedence detail beyond it.

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?

"Post a comment on an AI work board ticket" gives a specific verb and resource, and the qualifier "AI work board ticket" scopes it away from the support-ticket siblings (comment_support_ticket, create_support_ticket). It stops short of naming an alternative directly, but the resource qualifier is enough for an agent to disambiguate.

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?

The description supplies concrete use cases - findings, evidence, questions for colleagues, progress updates - and gives the rationale (the ticket timeline is the shared paper trail), which is clear when-to-use guidance. It offers no when-not-to guidance and names no alternative tool for cases like replying on a support ticket, so it falls short of a 5.

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.