Skip to main content
Glama

assign_ticket

Route a ticket to the station or session that will work it by station name, using T3, Linear, or GitHub identifiers; unstarted tickets start at todo.

Instructions

Give a ticket (T3, its id, or its Linear or GitHub identifier such as GH-12) to the station that works it, by the station's name (for example shop-build-m1). Only the orchestrator, or the person's own session, assigns. A ticket with no stage yet starts at todo.

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": "<ticket>",
      "holder": "<holder>"
    },
    "name": "assign_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
holderYes
ticketYes
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden; it does disclose an authorization constraint and a real side effect ("A ticket with no stage yet starts at todo"), which is genuinely useful beyond the schema. It says nothing about whether a ticket can be reassigned, what happens if the station or ticket is unknown, or any error/failure behavior for a mutation.

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?

Three short sentences, front-loaded with the core action and identifier formats, with the permission rule and stage default following logically. Minimal waste, though the parenthetical examples make the first sentence dense.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 not be explained, and the core semantics of ticket and holder are covered. However, this is an unannotated mutation with an undocumented project parameter and no statement about reassignment or failure modes, so it is adequate rather than complete.

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 description coverage is 0%, so the description must compensate, and it does well for two of three parameters: it enumerates accepted ticket identifier forms and gives a concrete station-name example for holder. The third parameter, project, is never mentioned despite having a default, leaving a gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Give a ticket ... to the station that works it") and clarifies both sides of the assignment: the ticket can be a T3 id or a Linear/GitHub identifier like GH-12, and the holder is a station name such as shop-build-m1. That is far more precise than the bare name, though it never names a sibling it differs from (e.g. hand_over, write_ticket).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states who may perform the assignment ("Only the orchestrator, or the person's own session, assigns"), which is a permission gate rather than a when-to-use rule. There is no guidance on choosing this over a related tool such as hand_over or write_ticket, so usage context is only implied.

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