Skip to main content
Glama

Release a held task

release_task
Idempotent

Drop the user's hold so someone else can take the task. Not possible once their proof is in review. Free.

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": {
      "campaign_id": "<campaign_id>",
      "task_id": "<task_id>"
    },
    "name": "release_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
campaign_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The description adds behavior beyond the annotations: a precondition that the release fails once proof is in review, and a cost disclosure ('Free'). For a mutation tool whose annotations are limited to idempotency and non-destructiveness, it does not explain effects on the original holder or error behavior, leaving a moderate gap.

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 terse sentences, front-loaded with the core action, then the precondition, then the cost note. No filler and nothing to trim.

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?

For a simple two-ID mutation the preconditions and cost are covered, and annotations handle safety and idempotency. However, the required parameters carry zero documentation and no output schema exists, so an agent must guess at ID semantics.

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 0% and the description says nothing about task_id or campaign_id — no format, scope, or lookup guidance. With two required parameters fully undocumented, the definition does not compensate for the schema gap; the ID names are self-describing only by inference.

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?

States a specific verb and resource ('Drop the user's hold') and its consequence ('so someone else can take the task'), which clearly inverts the sibling claim_task. It does not name the sibling explicitly, but the action is unambiguous.

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?

Gives a clear when-to-use context (freeing a held task for another taker) plus an explicit exclusion: 'Not possible once their proof is in review.' No named alternative is given for cases where the hold must persist, but the boundary condition is stated.

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.