Skip to main content
Glama

Hand back a task

taskhold_release

Put unfinished work back in To Do, with a note, when you stop and nobody has to answer (e.g. waiting on a captcha). Its steps go too, your label comes off, progress stays. Need the person? taskhold_block. Done tasks are refused.

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_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoWhere it stands and what's next
task_idYesThe ID of the task to hand back

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations (which only say non-readonly, non-destructive, closed-world) by enumerating side effects: subtask steps move too, the caller's label is removed, progress is preserved, and completed tasks are rejected. That is exactly the mutation context an agent needs before calling.

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?

Short and front-loaded: action first, then side effects, then the alternative, then the refusal rule. The telegraphic fragments ('Its steps go too, your label comes off, progress stays') read a bit clipped but each sentence carries information.

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?

Covers trigger, side effects, refusal case, and the competing tool — enough to call it correctly for a two-parameter mutation. It does not say what the call returns or whether the note is optional vs required, a minor gap given there is no output schema.

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 the schema already explains both task_id and note. The description's 'with a note' confirms the note is part of the handback but adds no format, length, or optionality detail beyond the schema.

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 concrete verb and outcome ('Put unfinished work back in To Do') plus the resource, and explicitly contrasts itself with taskhold_block. An agent can tell this apart from block/complete/unblock siblings without opening schemas.

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 an explicit trigger ('when you stop and nobody has to answer', with a captcha example) and names the alternative and its condition ('Need the person? taskhold_block'). It also states an exclusion: done tasks are refused.

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