Skip to main content
Glama

update_ticket

Idempotent

Update a ticket's status, priority, tier, assignee, or add a note, with a confirmation gate to preview changes before applying.

Instructions

Change ticket state: status, tier, priority, assignee, or an appended note.

WRITE OPERATION — CONFIRMATION GATE Calling without confirm=true performs a dry run: nothing changes, and the result returns applied: false with a changes list showing exactly which fields would move from what to what, plus CONFIRMATION_REQUIRED.

Show that preview to the user and get their agreement before calling again with confirm=true. Do not set confirm=true on the first call, and do not set it on the user's behalf because their intent seems obvious — the preview exists so a human sees the blast radius before state changes. Passing every field you were given at once is fine; the gate is about confirmation, not batching.

Pass only the fields you intend to change. Omitted fields are left alone. Passing note appends to the ticket's note trail; it never replaces it.

WHAT IT DOES NOT DO

  • Does not send anything to the requester. It changes internal ticket state only. draft_response composes customer-facing text.

  • Does not delete tickets, and cannot set a status outside the allowed values.

  • Does not validate that an escalation is appropriate. Recording tier 3 does not notify anyone; it records intent on the ticket.

FIELD VALUES status open | pending | resolved priority low | medium | high | critical tier 1 | 2 | 3 assignee technician username, or null to unassign note free text appended to the ticket's note trail

ERRORS TICKET_NOT_FOUND — no such ticket. CONFIRMATION_REQUIRED — expected on a dry run. Not a failure: it carries the preview. Show it to the user, then re-call with confirm=true. INVALID_FIELD — a value outside the allowed set; nothing was changed. Fix the value and retry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
tierNo
statusNo
confirmNo
assigneeNo
priorityNo
ticket_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
ticketNo
appliedYesTrue only when the change was actually committed.
changesNo
messageNo
ticket_idYes
error_codeNo
Behavior5/5

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

Annotations indicate idempotentHint=true and destructiveHint=false, which align with the description's confirmation gate and non-destructive dry run. Description adds context: dry run returns `applied: false` and a `changes` list, note appends rather than replaces, omitted fields are left unchanged. No contradictions.

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?

Description is long but well-structured with bold headers, bullet points for field values and errors. Every sentence adds value, though some redundancy (e.g., repeating 'confirm=true' instructions) could be trimmed. Front-loaded with main function and key warning.

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?

Given 5 sibling tools, the description thoroughly covers when to use, field values, error cases, and what the tool does not do. Output schema exists so return values are handled. No gaps; the tool is fully specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage, but the description fully compensates: it lists allowed values for status, priority, tier, assignee, and note, explains the confirm parameter's role, and clarifies that omitted fields are untouched. Adds meaning beyond the raw 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?

Clearly states the tool changes ticket state: status, tier, priority, assignee, or an appended note. Explicitly distinguishes from siblings by listing what it does NOT do (e.g., does not send to requester, does not delete tickets), which differentiates it from search_tickets, get_ticket, and draft_response.

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?

Provides explicit, step-by-step usage guidance: dry run first with confirm=false, show preview to user, get agreement, then call with confirm=true. Also warns against assuming user intent. Separates the confirmation gate from batching and explains error handling like CONFIRMATION_REQUIRED.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jackson-DM/msp-tools-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server