Skip to main content
Glama

Start a task

taskhold_start
Idempotent

Mark a task or step in progress when you begin it. Starting a step also starts its task. For new work, taskhold_begin files, plans and starts in one call. Returns the id, status and the next step's id when it has steps. Safe to repeat; it also resumes a blocked or done task. An unknown task_id fails with "Task not found".

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

Input Schema

NameRequiredDescriptionDefault
agentNoLabel shown to the person: "<client> in <repo folder>", e.g. "Claude Code in api-server" ("Claude Code" outside a repo).
task_idYesThe ID of the task to start

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / agent / description
      Previous value: -"Who is working, shown to the person: \"<client> in <repo folder>\", e.g. \"Claude Code in api-server\". Outside a repo just \"Claude Code\"."New value: +"Label shown to the person: \"<client> in <repo folder>\", e.g. \"Claude Code in api-server\" (\"Claude Code\" outside a repo)."
  2. Changed1 schema field changed
    • removedInput schema / properties / task_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so 'safe to repeat' is partly redundant, but the description adds real behavior beyond them: it resumes blocked or done tasks, returns id/status/next step id, and specifies the failure text for an unknown task_id. It stops short of describing what state transition is recorded or whether a start on an already-in-progress task records anything.

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?

Four short sentences, front-loaded with the core action, then routing, then return shape, then failure case. Every sentence supplies information an agent needs and none repeats the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description steps in to describe the return payload (id, status, next step id) and the error case. Combined with the sibling routing and resume behavior, an agent has everything needed for a two-parameter, non-destructive mutation.

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%, so both parameters (agent label and task_id UUID) are already documented in the schema. The description does not add format or meaning beyond it; baseline 3 applies since the schema carries the parameter burden.

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 ('mark a task or step in progress when you begin it') and immediately clarifies the parent/child rule that starting a step starts its task. It also names the sibling it is not (taskhold_begin, for new work), so an agent can route without opening either schema.

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?

Gives explicit when-to-use ('when you begin it'), an explicit alternative with its selection condition ('For new work, taskhold_begin files, plans and starts in one call'), and edge-case guidance (it resumes blocked or done tasks). Nothing is left to inference.

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