Skip to main content
Glama

checkout_task

Idempotent

Atomically acquire an exclusive TTL-based lock on a task to prevent simultaneous checkouts by other agents; the lock expires after ttl_minutes.

Instructions

Atomically acquire an exclusive lock on a task. Prevents other agents from checking out the same task simultaneously. The lock is TTL-based and will expire automatically after ttl_minutes (default 120). The lock gives the holder exclusive access to the task.

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

Input Schema

NameRequiredDescriptionDefault
task_idYesTask ID to check out.
ttl_minutesNoLock TTL in minutes (default 120).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is a non-read-only, idempotent, non-destructive, closed-world mutation. The description adds meaningful behavior beyond that: acquisition is atomic, the lock is exclusive, it is TTL-based, and it expires automatically after ttl_minutes. It does not describe what happens on contention or failure to acquire, so it falls short of a 5.

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?

The description is front-loaded and appropriately short for the tool. It is slightly repetitive, since "exclusive lock" and exclusive access are stated more than once, but the repetition is minor and does not obscure the key behavior.

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?

Given the rich annotations, fully described schema, and no output schema, the description covers the essential behavior: atomicity, exclusivity, TTL expiration, and default TTL. It could be more complete by mentioning release_task/extend_checkout or lock-acquisition failure behavior, but it is sufficient for an agent to understand the core operation.

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%, and the schema already documents both task_id and ttl_minutes including the default. The description restates the TTL semantics and default without adding syntax, constraints, or edge-case meaning beyond the schema, so baseline 3 is appropriate.

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 uses a specific verb and resource: "Atomically acquire an exclusive lock on a task." It immediately clarifies the concurrency purpose by stating it prevents other agents from checking out the same task simultaneously, which distinguishes it from generic task reads/updates and from the complementary release/extend tools.

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?

The description implies when the tool is useful by explaining that it prevents simultaneous checkout and grants exclusive access. However, it does not explicitly state when to call it versus alternatives such as release_task, extend_checkout, or get_task_context, nor does it describe exclusion conditions.

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