Skip to main content
Glama

task_release

Destructive

Releases an executor lease for a specified task using its task ID and token, freeing the executor for other simulation jobs.

Instructions

Release this executor's lease.

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>",
      "token": "<token>"
    },
    "name": "task_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
task_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and non-idempotent, so the safety profile is covered. Beyond that, the description adds nothing: it does not say whether other executors can then claim the task, whether the task is cancelled or merely unlocked, or what errors occur on an invalid or expired token.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with no filler, so it is concise and front-loaded. The brevity here is under-specification rather than economy, which limits the score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 described. But for a destructive, non-idempotent mutation with two fully undocumented required parameters, the definition should explain lease semantics and failure conditions; it leaves an agent unable to call this confidently.

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%, so the description is the only source of parameter meaning, and it explains neither task_id nor the distinction between the task identifier and the opaque token. "This executor's lease" only faintly hints that the token represents executor identity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and object ("release" a "lease"), which contrasts implicitly with claim-oriented siblings such as task_claim and task_background. However, it never defines what a lease is in this system or what releasing it accomplishes, so the purpose is only vaguely conveyed.

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 when-to-use guidance, no mention of preconditions (e.g., you must hold the lease), and no reference to any alternative tool. An agent must infer the lifecycle context entirely from the tool name.

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