Skip to main content
Glama

write_ticket

Create or update project tickets, set milestones and dependencies, and sync issues with Linear or GitHub while preventing duplicate titles.

Instructions

Add a ticket to the project's list, or change one when id is given (its id or T). When the project's tickets live in Linear or GitHub (link_tickets), a new ticket is created there, one per call: write the milestones first, then the tickets in dependency order. A repeat of the same title finds the issue again instead of making a second. depends_on is resolved to the tickets already written; milestone must be one already written. Its status, assignee and position come from Linear or GitHub, so naming them on a new ticket is refused. An existing Linear or GitHub ticket can be retitled, moved to a milestone and, for Linear, reordered here (position); its status, assignee and dependencies change there, and attach_working_doc links its working doc. For a project whose tickets live in Tares: status is todo, in_progress, done or canceled; position orders the list (a new ticket goes to the end); milestone is the name of a milestone written with write_milestone ("" takes it out of its milestone); depends_on lists the tickets (T or id) that must be done first ([] clears them); assignee is the person it is for (a person id or an email; an email nobody on the cell has is kept as written and the ticket shows as unowned; "" clears it), and assigning someone to a ticket of a private project adds them to it; naming an assignee needs an enterprise licence, without one leave it out. repo is the GitHub repo the ticket changes (owner/name), for a project that spans several repos ("" clears it). Returns the ticket with its label (T).

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": {
      "title": "<title>"
    },
    "name": "write_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
repoNo
titleYes
statusNo
projectNo
assigneeNo
positionNo
milestoneNo
depends_onNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so unusually well: idempotency ("a repeat of the same title finds the issue again instead of making a second"), a hidden side effect (assigning someone to a private project's ticket adds them to it), a licensing precondition ("naming an assignee needs an enterprise licence"), and the degraded case (an unknown email is kept as written and the ticket shows as unowned). It also discloses the return value (ticket with label T<n>).

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?

Purpose and mode switch are front-loaded and nearly every sentence carries new constraints, which justifies the length given 9 undocumented parameters. However, the Tares block is a single dense run-on with mixed concerns (status, position, milestone, depends_on, assignee, repo), so structure could be improved with grouping or line breaks.

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?

For a 9-parameter upsert tool with zero schema coverage and no annotations, the description covers creation, mutation, backend-specific divergence, ordering, side effects, and preconditions. An output schema exists, and the description still adds a short note on the returned label, so nothing essential is missing apart from the undefined `project` parameter.

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% across 9 parameters, so the description must do all the work, and it explains most of them concretely: status enum values, position ordering, milestone as a name written via write_milestone with "" clearing it, depends_on resolution against already-written tickets, assignee formats and clearing, and repo format (owner/name) with "" clearing. The gap is `project`, which is never defined (name vs id, required vs optional).

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 opening sentence states a specific verb and resource plus the create-vs-update switch: "Add a ticket to the project's list, or change one when `id` is given (its id or T<n>)." It also names the related siblings (link_tickets, write_milestone, attach_working_doc), so an agent can tell what this tool does and what it does not do without opening the schema.

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?

It gives explicit ordering rules ("write the milestones first, then the tickets in dependency order"), a one-ticket-per-call constraint, and conditional routing ("its status, assignee and dependencies change there, and attach_working_doc links its working doc"). It also states which fields are refused for Linear/GitHub-backed projects, which is a genuine when-not rule.

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