Skip to main content
Glama

Ticket assign

ticket_assign
Destructive

Assign an AI work board ticket to an agent, or clear its assignee. Identify the ticket by ticket_number or ticket_id, and the agent by agent_task_id or its exact agent_name; pass unassign true to clear it instead. Clearing returns the ticket to the board so the assign lane can staff it again, which is the repair for a ticket stuck on an agent that can no longer work it. A ticket keeps its assignee until it is reassigned, so designating a different board worker does not move it. Assigning to an agent that cannot currently work the board is allowed but answers with a warning naming the reason.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ticket_assign"
  }
}

Input Schema

NameRequiredDescriptionDefault
unassignNoClear the assignee instead of setting one (default false).
ticket_idNoThe ticket UUID. Optional when ticket_number is given.
agent_nameNoThe agent's exact name, as returned by list_agent_tasks.
agent_task_idNoThe agent task UUID to assign to.
ticket_numberNoThe per-organisation ticket number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false. The description adds real value beyond them: assignee persistence until reassignment, the board re-staffing effect of clearing, and that assigning an incapable agent succeeds but returns a warning naming the reason. It does not discuss required permissions or the exact response payload, keeping it from 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.

Conciseness4/5

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

The definition is front-loaded with the core action, then layers in the identification rules and edge cases in short declarative sentences. It runs five sentences and is dense but almost entirely substantive; a small amount of tightening around the persistence note is possible.

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?

With five optional parameters, no output schema, and a destructive mutation, the description does a good job: it explains identifier alternation, the clear path, and the warning behavior on an incapable agent. It does not state auth or permission requirements for a destructive operation, which is the main remaining gap.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: ticket_number and ticket_id are alternatives for identifying the ticket, agent_task_id and agent_name are alternatives for identifying the agent, and unassign flips the operation. That selection logic is genuinely useful beyond the per-field descriptions.

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 opens with a specific verb and resource ('Assign an AI work board ticket to an agent') and immediately covers the inverse operation ('or clear its assignee'), so an agent knows exactly what the tool mutates. It also names the identifying keys, making it distinguishable from ticket_update_status or ticket_comment siblings.

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?

It gives concrete when-to-use guidance: pass unassign true to clear, and clearing is 'the repair for a ticket stuck on an agent that can no longer work it.' It also clarifies a non-obvious case (designating a different board worker does not move the ticket). No sibling tool is named as an alternative, so it stops short of a 5.

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.