start-work

Start ticket

start_ticket

Claim a ticket by assigning it to yourself, marking it in progress, and returning the branch name plus full work brief before you write code.

Instructions

Claim a ticket: assign it to me, mark it in progress, and return the branch name to create plus the full work brief. Call this before writing any code.

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": {
      "number": "<number>"
    },
    "name": "start_ticket"
  }
}

Input Schema

Name	Required	Description	Default
`number`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full disclosure burden and does well on mutation effects (assigns to caller, sets in-progress) and on return payload. It omits failure behavior: whether claiming an already-claimed ticket errors or reassigns, whether the call is idempotent, and what permissions are required. Those gaps matter for a write operation with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly packed sentences with the effect and return value front-loaded and the call-ordering directive last. No filler or repetition.

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 one-parameter tool with no output schema, the description covers the inputs' role well enough and explains the return payload, which is more than most definitions do. The remaining shortfall is conflict/idempotency behavior, which an agent would want before invoking a state-changing claim.

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 single 'number' parameter is documented nowhere; the description only implies it via the phrase 'a ticket'. The name makes the intent guessable as a ticket number, but format, range, and where to obtain the value are left to inference.

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?

Uses a specific verb ('Claim') on a specific resource ('a ticket') and spells out the concrete effects: assignment to the caller, transition to in-progress, and a two-part return (branch name and work brief). That combination clearly separates it from siblings like set_ticket_status or get_ticket_context, which do not claim work or return a branch/brief.

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?

The instruction 'Call this before writing any code' gives a clear trigger condition and ordering relative to the coding workflow. It stops short of naming alternatives or exclusion cases, e.g., what to do if the ticket is already claimed or already in progress, which would have earned a 5.

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

Deploy Server