Skip to main content
Glama

release supervisor task

release_supervisor_task

Release a supervisor task claim by submitting its job ID and lease token so the task can be reassigned; prior tests remain counted against the attempt budget and a write-scope key is required.

Instructions

Release claim. Previous tests still count against the attempt budget. Requires a write-scope key.

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": {
      "jobId": "<jobId>",
      "leaseToken": "<leaseToken>"
    },
    "name": "release_supervisor_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes
leaseTokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it does add two genuinely useful facts: releasing does not reset the attempt budget, and a write-scope key is required. However, for a mutation tool it omits what matters most - whether the claim is destroyed, what happens if the leaseToken is stale or mismatched, and whether the operation is idempotent.

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?

Three short, front-loaded sentences with no filler; the action comes first and the constraints follow. It is terse to the point of being telegraphic, but nothing is wasted.

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 small two-parameter tool with no output schema this covers the auth requirement and the budget caveat, which is a reasonable minimum. It remains incomplete on parameter meaning and on the post-release state of the claim, which are the questions an agent will actually have.

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 description coverage is 0% and the description never mentions jobId or leaseToken, so neither parameter's meaning is explained anywhere. The phrase "write-scope key" gestures at authorization but does not tell the agent that leaseToken (a fixed 64-character string) identifies the specific claim being released.

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?

"Release claim" gives a specific verb plus resource, and the tool name anchors it to supervisor tasks, so an agent can tell this undoes a claim rather than applying or reporting one. It stops short of naming or contrasting any sibling explicitly (e.g. claim_supervisor_task or apply_supervisor_task), so it is clear but not differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus the other supervisor-task tools, nor any precondition such as needing an active claim first. The attempt-budget sentence hints that releasing is useful before testing, but that inference is left entirely to the agent.

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