Skip to main content
Glama

continue_next

Records the outcome and note for the current card, extends your checkout, and keeps the card with you so you can continue working immediately without interruption.

Instructions

End your turn with a piece of work done and more to do right away: records the outcome and the comment, keeps the card with you and extends your checkout. Reading the card or writing a plan is not a piece of work — keep working instead. Refused with 409 when you do not hold the card's checkout.

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": {
      "task_id": "<task_id>",
      "note": "<note>"
    },
    "name": "continue_next"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYesWhat was done this turn and what comes next, max 4096 chars.
task_idYesThe card you are working on (UUID or 6-12 hex short id).
turn_idNoOptional turn id within the session (max 200 chars), copied onto the outcome.
session_idNoOptional runner session id (max 200 chars), copied onto the recorded outcome and wait.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.7

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a non-readonly, non-idempotent, non-destructive mutation, and the description adds behavioral facts beyond them: the checkout is extended, the outcome and comment are persisted, and the call is refused with 409 if the caller does not hold the checkout. That refusal condition is genuinely useful pre-call knowledge, though retry semantics after a 409 are not spelled out.

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?

Three tight sentences, front-loaded with the trigger condition and followed by the anti-pattern and the failure mode. No filler; the slightly compressed opening clause costs it a point but nothing is wasted.

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?

For a four-parameter mutation with no output schema, the description covers the side effects and the 409 failure well, but says nothing about what the call returns (recorded outcome, wait/checkout state) or what happens to turn_id/session_id propagation beyond the schema. Adequate but not fully closed.

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 100%, so all four parameters, including the note contents and the id/short-id format, are already documented in the schema. The description adds no format, limits, or meaning beyond 'records the outcome and the comment,' leaving the baseline of 3 appropriate.

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 action with concrete effects: records the outcome and comment, keeps the card checked out, extends the checkout. That distinguishes it meaningfully from a plain finish_task or extend_checkout, though it never names the sibling to use instead, so the differentiation is inferred rather than explicit.

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?

Gives real when-to-use guidance ('piece of work done and more to do right away') and, unusually, an explicit when-not: 'Reading the card or writing a plan is not a piece of work — keep working instead.' No alternative tool is named for the finish-the-card case, which is the only gap.

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