Skip to main content
Glama

reply_ticket

Adds a message to an existing ticket of the user ON THEIR BEHALF (marked "via AI"). Meant for use only when the user asks for it or approves it. Permission tickets; 5 messages an hour for the AI; 3 plain-text attachments at most. Requires a JusticeLibre account (OAuth sign-in); without one, the tool says so.

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": {
      "ticket_id": "<ticket_id>",
      "message": "<message>"
    },
    "name": "reply_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesThe message, 4,000 characters at most.
ticket_idYesTicket "t_…".
attachmentsNoAt most 3, plain text only.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the AI attribution marking, an hourly rate limit of 5 messages, a cap of 3 plain-text attachments, permission-ticket behavior, and the OAuth account prerequisite. These are exactly the operational constraints an agent needs before committing to a write.

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?

Compresses purpose, consent gating, attribution, rate limit, and auth requirements into three dense sentences, front-loading the on-behalf-of semantics. The all-caps emphasis is stylistically noisy but does not obscure meaning.

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 mutation tool with an output schema, the definition covers consent, attribution, quotas, attachment limits, and authentication failure behavior. An agent has everything needed to decide whether to call it and what to expect.

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 ticket_id, message, and attachments are already documented with types, formats, and limits. The description reinforces the plain-text and 3-attachment constraints but adds no new syntax or format guidance beyond the schema.

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 (adds a message to an existing ticket) with the crucial qualifier that it posts on the user's behalf and is marked "via AI". This clearly distinguishes it from open_ticket, which would create a new ticket rather than append to one.

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?

Explicitly gates use on the user asking for it or approving it, and notes the tool reports its own failure when no JusticeLibre account exists. It stops short of naming a concrete alternative action (e.g., telling the user to reply manually), so it is strong but not exhaustive.

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.

Resources