Skip to main content
Glama

Coline

Let a task go

release_task

Releases a task this agent holds. It goes back as it was: its status before you took it, and still marked for you if your person marked it.

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": {
      "workspace": "<workspace>",
      "taskboardId": "<taskboardId>",
      "taskId": "<taskId>"
    },
    "name": "release_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
taskboardIdYes

Output Schema

NameRequiredDescriptionDefault
releasedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the annotations, it discloses the post-condition: the task reverts to its prior status and preserves the human's assignment marker. That is genuinely useful state-restoration context for a mutating tool. It leaves gaps around permissions, failure when the task is not held, and why idempotentHint is false for an operation that sounds repeatable.

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?

Two short sentences, front-loaded with the action and followed by the state outcome; no filler. The phrasing "still marked for you if your person marked it" is slightly colloquial and ambiguous, which costs a little clarity.

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?

An output schema exists, so return values need not be explained, and the description covers the main side effect. However, for a three-parameter mutation with weak schema documentation, it omits how to identify the task/taskboard and error or permission behavior, leaving real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% — only workspace is documented — and the description adds nothing about taskId or taskboardId (e.g., how to obtain a taskboard id, or whether the task must belong to that board). The low-coverage case requires the description to compensate, and it does not.

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?

The description states a specific verb and resource ("Releases a task") and narrows scope to one the agent currently holds, which implicitly distinguishes it from take_task/hand_task_outside. It stops short of naming any sibling explicitly, so it is clear but not fully differentiated.

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?

"a task this agent holds" implies the precondition for calling it, but there is no explicit when-to-use/when-not statement, no mention of what happens if the agent does not hold the task, and no named alternative for cases where release is wrong.

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