Skip to main content
Glama

update_ticket

Update a project ticket by ticket_id (from create_ticket or list_tickets): change its status, priority, title or description. Only the fields you pass change.

Example: update_ticket(ticket_id="...", status="In Progress")

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>"
    },
    "name": "update_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
statusNo
priorityNo
ticket_idYesThe ticket's id
descriptionNoReplaces the whole description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses partial-update semantics ('Only the fields you pass change'), which is non-obvious mutation behavior, but says nothing about permissions, whether status transitions are constrained, error behavior for invalid enums, or reversibility.

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?

Two tight sentences plus a one-line example; the partial-update rule is front-loaded and nothing is redundant.

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 5-parameter mutation tool with no annotations and no output schema, the definition covers the updatable fields and the partial-update contract well. It stops short of describing the return value or failure modes, which an agent would need for a write operation with no structured safety hints.

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?

Coverage is 40%, so the description should compensate more than it does. It maps the four updatable fields and clarifies that ticket_id comes from create_ticket/list_tickets, but adds no format expectations for title/description beyond what the schema already says (including the 'Replaces the whole description' note).

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 ('Update') and resource ('project ticket'), and grounds the identifier by naming create_ticket/list_tickets as the source of ticket_id. An agent can distinguish this from create_ticket or list_tickets without inspecting either 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?

Gives clear usage context: change status/priority/title/description and only the passed fields change, plus a concrete example call. It lacks explicit exclusions (e.g., when to prefer update_block or update_checklist_item over this), so it falls just short of full routing guidance.

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