AALY

add_comment

Add a reply to the comment thread of a support ticket or feature request you can already see (get_support_ticket / list_feature_requests). Use it to answer a question from the AALY team, add detail they asked for, or report that a fix did or did not work. It only ever appends a comment; it cannot change status or any other field.

The comment is attributed to the signed-in user and labelled as coming from an agent (pass client_name, e.g. 'Claude Code', to say which). Read the thread first with get_support_ticket so you don't repeat what's already there. A closed ticket takes no more comments - if it's still a problem, file a new ticket and mention the old id. A ticket or request with status 'on_hold' is parked on purpose; its holdReason says why - you can still comment.

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": {
      "record_type": "<record_type>",
      "record_id": "<record_id>",
      "text": "<text>"
    },
    "name": "add_comment"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	The comment, plain text, up to 5000 characters.
`record_id`	Yes	The ticket id (SPT...) or feature request id (FRQ...).
`client_name`	No	The connecting client, e.g. 'Claude Code', 'Cursor'.
`record_type`	Yes	Which kind of record the comment goes on.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses that the comment is attributed to the signed-in user, labelled as agent-authored via client_name, that the call is append-only, and that closed tickets reject comments while on_hold tickets accept them. These are exactly the non-obvious behavioral facts an agent needs before invoking a write 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?

Front-loaded with the purpose and the append-only boundary, then usage, then edge cases in a logical order. Three short paragraphs are efficient, though the closing on_hold sentence is a low-probability edge case that could be trimmed.

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

Completeness5/5

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

For a non-idempotent write with four documented params and no output schema, the description covers purpose, attribution, preconditions (read the thread first), failure conditions (closed ticket), and the fallback path. Nothing needed to call it correctly is missing.

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%, including the 5000-character text limit, the SPT/FRQ id formats, and the client_name example values, so the description's mention of client_name ('to say which') and record kinds largely restates the schema. Baseline 3 is appropriate — it adds framing but no format or constraint detail the schema lacks.

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?

States a specific verb and resource ('Add a reply to the comment thread of a support ticket or feature request') plus the defining constraint that it only appends and cannot mutate other fields. It distinguishes itself from the large create_/update_/delete_ sibling set by naming the records it attaches to and the read tools that precede it.

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?

Gives three concrete use cases (answer a question, add requested detail, report whether a fix worked), names the prerequisite read tool (get_support_ticket) and explicitly rules out commenting on closed tickets, routing that case to filing a new ticket. The on_hold nuance is spelled out rather than left to inference.

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

All AALY tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?