Skip to main content
Glama

builder_brief

Returns ticket briefing—stage, holder, PR, verdict, docs, milestones, acceptance checks, dependencies, assumptions, and prior work—to help agents start or resume work; start moves new tickets to doing.

Instructions

Start every ticket here, and again after a revive: one read with where the ticket stands (stage, holder, PR, verdict), its working doc, its milestone and acceptance checks, the state of what it depends on, the project's AGENTS.md (it wins over the generic flow) and the shared one, open assumptions and desk questions on it, and where you left off (checks recorded, Codex, earlier review rounds, the crew's latest messages). start=True also moves a ticket that has not been started to doing, so starting a ticket is this one call; a ticket already in review, changes, blocked or merged keeps its stage.

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": "builder_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
startNo
ticketYes
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.8/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 load and does well: it discloses that `start=True` mutates a not-yet-started ticket to 'doing' while tickets already in review/changes/blocked/merged keep their stage. That is a precise side-effect disclosure. Gaps remain on permissions, error behavior for unknown tickets, and whether the call is otherwise non-mutating.

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 directive ('Start every ticket here') followed by the return inventory, then the `start` side effect. The middle sentence is a dense run-on list, but nearly every clause carries information an agent needs.

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 the enumerated return values are arguably redundant, yet the description still omits the `project` parameter's meaning and ticket identifier expectations. For a 3-param entry-point tool, that leaves a meaningful hole.

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 coverage is 0%, so the description must compensate. It explains `start` thoroughly (default, side effect, stage-exception rules) but never explains the required `ticket` identifier's format or the `project` parameter at all, leaving two of three params undocumented.

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?

States a specific verb and resource: 'one read with where the ticket stands (stage, holder, PR, verdict)' plus a detailed inventory of what the brief aggregates. It is clearly distinguishable from a generic read, though it never names the close siblings (get_ticket, review_brief) that an agent might otherwise pick.

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?

'Start every ticket here, and again after a revive' gives explicit when-to-use guidance and a re-entry condition after a revive. It does not state when NOT to use it or point to alternatives such as get_ticket for a narrower read.

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