Skip to main content
Glama
delega-dev

delega-mcp

by delega-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

release_task

Return a claimed task to the open queue without completing it, so another agent can pick it up. Add a handoff note so the next agent resumes work.

Instructions

Release a task you have claimed back to the queue without completing it. Use when you cannot finish the work or another agent should take over — the task returns to open status and becomes immediately claimable. Leave a handoff note so the next agent resumes instead of restarting. Hosted API only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
handoffNoOptional handoff note: where you left off / why you stopped (e.g. 'migration written, blocked on prod DB creds'). The next agent to claim this task sees it as a 'Resuming from' line. If omitted, the task's last session-state detail is preserved as the note.
task_idYesThe claimed task ID to release

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.19.0
    • removedInput schema / properties / task_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / task_id / type
      Added value: +[
+  "string",
+  "number"
+]
  2. Addedv1.18.2
  3. Removedv1.13.1
  4. Addedv1.9.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the state transition (back to open, immediately claimable), the visibility of the handoff note to the next claimant, and an environment constraint ('Hosted API only'). It does not cover permission/auth requirements or what happens if the task isn't currently claimed by the caller.

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?

Three tight sentences: purpose/effect, when to use, and a practical tip. The state-change consequence is front-loaded and nothing is padded.

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 two-parameter mutation with no output schema and no annotations, the description covers state effects and handoff semantics adequately. Missing permission requirements and error/edge behavior (e.g., releasing an unclaimed or already-completed task) keep it just short of fully complete.

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 the schema already fully documents both task_id and handoff, including the fallback behavior when handoff is omitted. The description reinforces why to supply handoff but adds no syntax or format detail beyond the schema — the baseline 3 applies.

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?

The description names a specific verb ('Release') and resource ('a task you have claimed') and states the resulting state change ('returns to open status and becomes immediately claimable'). It is clearly distinguishable from siblings like complete_task, claim_task, and set_task_state.

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?

It gives an explicit trigger condition: 'Use when you cannot finish the work or another agent should take over.' That effectively routes the agent away from complete_task, though no sibling tool is named as an alternative and no negative exclusions are stated.

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

Deploy Server

Other Tools