Skip to main content
Glama

Take the next task

taskhold_next

Work the list as a queue: takes the next To Do task (highest priority, then oldest by default) and starts it and its first step. Atomic: no 2 agents get the same task. Returns the task, steps, project notes and next call, or that To Do is empty.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "taskhold_next"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNoLabel shown to the person: "<client> in <repo folder>", e.g. "Claude Code in api-server" ("Claude Code" outside a repo).
projectNoProject name, e.g. the repo folder ("api-server"). Any case, or an id. Unknown names match nothing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses the side effect (starts the task and its first step), the concurrency guarantee ('no 2 agents get the same task'), the exact return payload (task, steps, project notes, next call), and the empty-queue case. It does not say what happens on failure mid-start or whether the atomic claim can time out.

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?

One dense sentence plus a short fragment, front-loaded with the mental model ('as a queue') before the mechanics. Every clause carries information: ordering, atomicity, return shape, empty case.

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?

Complete enough for a two-optional-parameter tool with no output schema: ordering, atomicity, return contents and empty behavior are all covered. The gap is how the optional project/agent parameters scope selection, which matters for correct invocation.

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 100% and both parameters are self-documented, so the baseline is 3. The description adds nothing about them, notably leaving open whether an optional 'project' argument narrows the queue to that project's To Do tasks.

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?

States a specific verb and resource ('takes the next To Do task ... and starts it and its first step') plus the exact selection rule (highest priority, then oldest). The framing 'Work the list as a queue' distinguishes it from taskhold_start/taskhold_begin, which operate on an identified task.

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 queue framing and the 'To Do' precondition, but there is no explicit when-not guidance and no sibling is named as the alternative (e.g., 'if you already have a task id, use taskhold_start instead'). An agent must infer the routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources