Skip to main content
Glama

ticket_update

Update project ticket status, priority, or details to track progress and manage tasks in the tpm-mcp server.

Instructions

PROJECT MANAGEMENT (TPM): Update a ticket's status, priority, or details.

USE THIS TOOL WHEN:

  • User says "I just finished implementing X" - mark related ticket as done

  • User says "I've pushed commits for X" - update status based on progress

  • Marking work as in-progress, done, or blocked

  • Changing priority of a ticket

  • User completes a ticket and needs to update status

  • Adding/updating tags or assignees

Use roadmap_view first to find the ticket_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ticket_idYesTicket ID (e.g., FEAT-001)
titleNoNew title
descriptionNoNew description
statusNoNew status
priorityNoNew priority
tagsNoUpdated tags
assigneesNoUpdated assignees

Implementation Reference

  • Registers the ticket_update tool with the MCP server, defining its name, description, and input schema.
            Tool(
                name="ticket_update",
                description="""PROJECT MANAGEMENT (TPM): Update a ticket's status, priority, or details.
    
    USE THIS TOOL WHEN:
    - User says "I just finished implementing X" - mark related ticket as done
    - User says "I've pushed commits for X" - update status based on progress
    - Marking work as in-progress, done, or blocked
    - Changing priority of a ticket
    - User completes a ticket and needs to update status
    - Adding/updating tags or assignees
    
    Use roadmap_view first to find the ticket_id.""",
                inputSchema={
                    "type": "object",
                    "properties": {
                        "ticket_id": {"type": "string", "description": "Ticket ID (e.g., FEAT-001)"},
                        "title": {"type": "string", "description": "New title"},
                        "description": {"type": "string", "description": "New description"},
                        "status": {
                            "type": "string",
                            "enum": ["backlog", "planned", "in-progress", "done", "blocked"],
                            "description": "New status",
                        },
                        "priority": {
                            "type": "string",
                            "enum": ["critical", "high", "medium", "low"],
                            "description": "New priority",
                        },
                        "tags": {
                            "type": "array",
                            "items": {"type": "string"},
                            "description": "Updated tags",
                        },
                        "assignees": {
                            "type": "array",
                            "items": {"type": "string"},
                            "description": "Updated assignees",
                        },
                    },
                    "required": ["ticket_id"],
                },
            ),
  • The handler function in _handle_tool that processes the ticket_update tool call, validates input using TicketUpdate model, and calls the DB update method.
    if name == "ticket_update":
        update = TicketUpdate(
            title=args.get("title"),
            description=args.get("description"),
            status=TicketStatus(args["status"]) if args.get("status") else None,
            priority=Priority(args["priority"]) if args.get("priority") else None,
            tags=args.get("tags"),
            assignees=args.get("assignees"),
        )
        ticket = db.update_ticket(args["ticket_id"], update)
        if ticket:
            # Return minimal confirmation to avoid context bleed
            return f"Updated ticket: {ticket.id} - {ticket.title} [{ticket.status.value}]"
        return f"Ticket {args['ticket_id']} not found"
  • Pydantic BaseModel defining the schema for ticket update parameters, used for input validation.
    class TicketUpdate(BaseModel):
        title: str | None = None
        description: str | None = None
        status: TicketStatus | None = None
        priority: Priority | None = None
        assignees: list[str] | None = None
        tags: list[str] | None = None
        related_repos: list[str] | None = None
        acceptance_criteria: list[str] | None = None
        blockers: list[str] | None = None
        metadata: dict[str, Any] | None = None
  • Core database helper method that dynamically builds and executes SQL UPDATE statement for the tickets table based on non-None fields in TicketUpdate.
    def update_ticket(self, ticket_id: str, data: TicketUpdate) -> Ticket | None:
        updates = []
        params = []
        if data.title is not None:
            updates.append("title = ?")
            params.append(data.title)
        if data.description is not None:
            updates.append("description = ?")
            params.append(data.description)
        if data.status is not None:
            updates.append("status = ?")
            params.append(data.status.value)
            if data.status == TicketStatus.IN_PROGRESS:
                updates.append("started_at = ?")
                params.append(self._now())
            elif data.status in (TicketStatus.DONE, TicketStatus.COMPLETED):
                updates.append("completed_at = ?")
                params.append(self._now())
        if data.priority is not None:
            updates.append("priority = ?")
            params.append(data.priority.value)
        if data.assignees is not None:
            updates.append("assignees = ?")
            params.append(_to_json(data.assignees))
        if data.tags is not None:
            updates.append("tags = ?")
            params.append(_to_json(data.tags))
        if data.related_repos is not None:
            updates.append("related_repos = ?")
            params.append(_to_json(data.related_repos))
        if data.acceptance_criteria is not None:
            updates.append("acceptance_criteria = ?")
            params.append(_to_json(data.acceptance_criteria))
        if data.blockers is not None:
            updates.append("blockers = ?")
            params.append(_to_json(data.blockers))
        if data.metadata is not None:
            updates.append("metadata = ?")
            params.append(_to_json(data.metadata))
    
        if not updates:
            return self.get_ticket(ticket_id)
    
        params.append(ticket_id)
        self.conn.execute(f"UPDATE tickets SET {', '.join(updates)} WHERE id = ?", params)
        self.conn.commit()
        return self.get_ticket(ticket_id)
Behavior4/5

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

With no annotations provided, the description carries full burden. It clearly indicates this is a mutation tool ('Update'), specifies what fields can be modified (status, priority, details), and mentions the prerequisite of finding ticket_id via roadmap_view. However, it doesn't disclose potential side effects, permission requirements, or rate limits that would be helpful for a mutation operation.

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?

The description is well-structured with clear sections (purpose statement, usage guidelines, prerequisite). Most sentences earn their place by providing concrete value, though the usage examples could be slightly more concise. The information is front-loaded with the core purpose stated first.

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 mutation tool with 7 parameters, 100% schema coverage, and no output schema, the description provides strong usage context and distinguishes from siblings. It covers when to use the tool and references the prerequisite tool. The main gap is lack of information about what the tool returns or confirmation of successful updates.

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%, providing complete parameter documentation. The description adds minimal value beyond the schema by mentioning 'status, priority, or details' and referencing 'tags or assignees' in usage examples, but doesn't provide additional semantic context about parameter interactions or constraints. This meets the baseline for high schema coverage.

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?

The description clearly states the tool's purpose with specific verbs ('Update a ticket's status, priority, or details') and identifies the resource ('ticket'). It distinguishes from siblings like ticket_create (create vs update), ticket_get (retrieve vs modify), and roadmap_view (view vs update).

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?

The description provides explicit usage guidelines with concrete examples ('User says "I just finished implementing X" - mark related ticket as done'), clear when-to-use scenarios ('Marking work as in-progress, done, or blocked'), and a specific alternative directive ('Use roadmap_view first to find the ticket_id'). This gives comprehensive guidance on tool selection.

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/urjitbhatia/tpm-mcp'

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