Skip to main content
Glama

loop_task_claim

Atomically claims a task using CAS lease epoch and fence token, returning a compact resume packet so distributed workers can safely resume without duplicate execution.

Instructions

Atomically claim a task with CAS lease_epoch, fence_token, and compact resume_packet.

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": {
      "worker_id": "<worker_id>"
    },
    "name": "loop_task_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
regimeNo
task_idNo
namespaceNo
worker_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/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 disclose real behavioral traits: atomicity, CAS concurrency control, and lease/fence-token semantics that suggest mutual exclusion and safe resumption. However, it says nothing about what a failed CAS returns, whether claims expire or must be released, or what the caller should do on conflict, so key concurrency behavior remains opaque.

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?

A single front-loaded sentence with the action first and qualifiers after — no filler or boilerplate. It loses a point only because the compressed jargon makes the sentence harder to act on than a slightly longer phrasing would.

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?

A concurrency-sensitive claim operation with no annotations, no output schema, and 0% parameter documentation needs far more: parameter meanings, claim lifetime, conflict behavior, and what a resume_packet contains. The description supplies only a high-level label plus unexplained terms, leaving the agent under-equipped to invoke it correctly.

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% for four parameters, so the description needed to compensate and does not: worker_id, task_id, namespace, and regime go entirely unexplained. Worse, the terms it does name (lease_epoch, fence_token, resume_packet) are not parameters in the schema, so they add no parameter meaning.

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?

"Atomically claim a task" is a specific verb plus resource that an agent can distinguish from siblings like enqueue or checkpoint. The trailing clause ("CAS lease_epoch, fence_token, and compact resume_packet") is dense internal jargon that names concepts rather than clarifying the operation, keeping it from a 5.

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 guidance on when to claim versus enqueue or checkpoint, no prerequisites, and no statement about what to do on failure. The word "atomically" implies a concurrency-sensitive workflow, but the agent is left to infer ordering and retry behavior entirely.

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