Skip to main content
Glama

Update an IT ticket

ticket_update
DestructiveIdempotent

Update a support ticket's status, priority, assignee, or add a comment; preview changes by default and set confirm=true to apply. Closing requires admin; agents can resolve.

Instructions

Change a ticket’s status, priority or assignee and/or add a comment. Dry run by default; confirm=true applies it. Closing a ticket needs the admin role (agents can resolve). Requires role: agent.

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": {
      "id": "<id>"
    },
    "name": "ticket_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTicket id, e.g. IT-1003
statusNo
commentNo
confirmNofalse (default) = dry run that only previews the change. true = actually apply it. Ask the user before sending true.
priorityNo
assignee_idNoEmployee id, e.g. E004

Output Schema

NameRequiredDescriptionDefault
ticketYes
changesYes
dry_runYes
next_stepNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered, and the description adds genuinely new context: the two-phase dry-run/confirm protocol and the role split between agents (resolve) and admins (close). It does not spell out what a dry-run response contains or whether a status change notifies anyone, which is why it falls short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, each carrying a distinct load: what changes, how it is applied, and who is permitted. The dry-run default is front-loaded where an agent will see it before deciding to call.

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?

An output schema exists, so return values need no explanation, and the annotations plus the role/preview rules make the mutation behavior clear. The remaining gap is per-field semantics for status and assignee_id, which neither the schema nor the description fills in.

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 50%: id and confirm are already documented in the schema, and the description restates confirm's semantics rather than extending them. The enum-constrained parameters (status, priority, assignee_id) get no added meaning such as allowed transitions or assignment constraints, so the description does not compensate for the undocumented half.

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?

Names a specific verb (change/update) plus the exact resources it mutates: status, priority, assignee and comment. An agent can distinguish it from ticket_create and ticket_get purely from the description without opening the schema.

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?

States the invocation condition clearly: dry run is the default and confirm=true commits the change, plus explicit role prerequisites (agent required, admin needed to close). It does not name a sibling alternative, but for a mutation tool the when-to-use framing is unambiguous.

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