Skip to main content
Glama

set_stage

Move a held ticket between stages—doing, review, changes, merged, or blocked—while recording checks and PR details. Refuses tickets owned by another station.

Instructions

Move a ticket you hold: stage is doing (you started), review (its PR is up: pass pr, the pull request's URL), changes (the reviewer asked for changes), merged, or blocked (say why in reason). Only the releaser marks a ticket shipped. A ticket held by another station is refused; ask the orchestrator. For a ticket that lives in Linear or GitHub, also move it there (Linear's own tools, gh for GitHub). Name your branch factory/ (factory/T3) so Tares finds the pull request on its own too. Asking for review, pass the checks you ran as checks ([{command, result, commit, broke_test}, ...]) instead of one add_check call each; they are recorded before the stage moves.

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

Input Schema

NameRequiredDescriptionDefault
prNo
stageYes
checksNo
reasonNo
ticketYes
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral load and does well: it discloses ownership/permission constraints, the refusal path for tickets held elsewhere, an external side effect (also move the ticket in Linear or GitHub), and ordering semantics (checks are recorded before the stage moves). It stops short of stating whether stage transitions are reversible or what is returned on refusal, which are the remaining gaps for a mutation tool.

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?

Front-loaded with the core action and the stage vocabulary, then the constraints, then the batching advice — a sensible ordering. The prose is dense and somewhat run-on in places (the parenthetical about `pr` wrapping mid-sentence, the Tares branch aside), but nearly every clause conveys a rule the caller needs.

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 six-parameter mutation tool with no annotations, this covers ownership, refusal, side effects, and the compound `checks` payload, and an output schema exists so return values need no explanation. The unaddressed `project` parameter is the one substantive omission an agent would have to guess at.

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 0%, so the description must compensate, and it largely does: `stage` gets a full value list, `pr` is defined as the pull request URL, `reason` is tied to the blocked stage, and `checks` is given an explicit element shape ([{command, result, commit, broke_test}, ...]). The `project` parameter is never mentioned, and `ticket`'s expected format is only indirectly implied by the factory/<ticket> branch convention.

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?

Opens with a specific verb+resource ("Move a ticket you hold") and immediately enumerates the exact stage domain: doing, review, changes, merged, blocked. It also positions itself against siblings by telling the agent to batch checks here "instead of one add_check call each," so the boundary with add_check is explicit.

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?

Each stage value comes with the condition that selects it (doing = you started, review = PR is up, changes = reviewer asked, blocked = must supply reason). It states an exclusion ("Only the releaser marks a ticket shipped"), a failure mode ("A ticket held by another station is refused; ask the orchestrator"), and a required follow-up for externally-hosted tickets.

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