Skip to main content
Glama

get_ticket

Retrieves a ticket by Tares ID, number, Linear or GitHub identifier, returning its working doc, status, assignee, pull request details, history, and crew messages so you can act on it.

Instructions

One ticket, by its Tares id, its number (T3), its Linear identifier (for example ENG-12) or its GitHub identifier (for example GH-12), with the body of its working doc, who holds it and where it stands, who it is for (assignee, or assignee_raw when that person is not on this cell), its pull request as GitHub has it (head, CI, the reviewer's verdict, merged), its history, and the crew's messages about it: everything you need to work on it.

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

Input Schema

NameRequiredDescriptionDefault
ticketYes
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral load and does so substantively: it discloses that the working doc body, holder, status, PR state (head, CI, reviewer verdict, merged), history, and crew messages are all included, and explains the `assignee` vs `assignee_raw` fallback when the person is off-cell. It stops short of stating read-only intent, error behavior for unknown ids, or cost/latency of assembling all that data.

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?

It is front-loaded with the lookup keys before the payload catalog, which is the right order. The payload section is a dense single-sentence list that is slightly hard to parse in one pass but every clause adds distinct information rather than filler.

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 two-parameter read tool with an output schema present, the description covers nearly everything an agent needs to invoke it: valid id forms, the returned payload, and the assignee resolution quirk. The only meaningful gap is the unexplained `project` parameter, which matters more because ids may repeat across projects.

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 0%, so the description must compensate. It does an excellent job on `ticket`, enumerating four accepted identifier formats with examples, which would otherwise be invisible. The second parameter, `project` (default empty), gets no mention at all, leaving the agent to guess whether it scopes the lookup or disambiguates ids across projects.

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 makes the resource and scope unmistakable: a single ticket, retrieved by one of four identifier forms (Tares id, number like T3, Linear ENG-12, GitHub GH-12), with a concrete inventory of what comes back. It never names a sibling or says 'use X for lists,' so differentiation is left implicit, but no agent could confuse it with assign_ticket or write_ticket on purpose alone.

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?

Usage is implied by the closing phrase 'everything you need to work on it,' which frames this as the prerequisite lookup before acting on a ticket. There is no explicit when-not guidance, no mention of what to do if the ticket does not exist, and no routing to a search/list tool for finding an id you don't already have.

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