Skip to main content
Glama

loop_task_checkpoint

Persist fenced task progress with lease_epoch validation to reject stale or zombie writers, enabling safe checkpointing and resumable workflows.

Instructions

Persist fenced task progress; rejects zombie/stale lease_epoch writers.

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>",
      "worker_id": "<worker_id>",
      "lease_epoch": "<lease_epoch>",
      "fence_token": "<fence_token>",
      "checkpoint": "<checkpoint>"
    },
    "name": "loop_task_checkpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
completedNo
worker_idYes
checkpointYes
fence_tokenYes
lease_epochYes

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 behavioral burden. It does disclose one genuinely useful trait beyond structure — stale or zombie writers are rejected — which tells the agent this is a fenced, fail-on-stale write rather than an unconditional upsert. However, it says nothing about idempotency, what happens to a previously stored checkpoint, required permissions, or the failure mode/return shape.

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 clause with zero filler; the guarding behavior is stated right after the action. The terseness is efficient, though the density of internal jargon borders on under-specification for a six-parameter tool.

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?

For a six-parameter mutation with a nested object, no annotations, no output schema, and zero schema descriptions, the definition is substantially incomplete. The one behavioral disclosure does not compensate for the missing parameter semantics, preconditions, or result behavior an agent needs to call this safely.

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% across six parameters, five of them required, including a nested 'checkpoint' object. The description only hints at fence_token and lease_epoch via 'fenced' and 'zombie/stale lease_epoch'; it offers no meaning for task_id, worker_id, completed, or the shape of checkpoint, so most parameters remain undocumented in both places.

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: 'Persist ... task progress', with the qualifier 'fenced' signalling the write is guarded. The verb 'persist progress' is distinct from sibling operations like claim and enqueue, so an agent can tell roughly what this tool is for, though the jargon ('fenced', 'lease_epoch') assumes familiarity.

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 explicit when-to-use or when-not guidance and no sibling is named as an alternative. The clause 'rejects zombie/stale lease_epoch writers' implies a precondition (you must hold a current lease epoch) but never states it as a usage rule.

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