Skip to main content
Glama

task_claim

Destructive

Acquire or renew an exclusive writer lease for a simulation task to ensure only the active owner can write and expired tokens cannot modify results.

Instructions

Acquire or renew the single writer lease. An expired token can never write.

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

Input Schema

NameRequiredDescriptionDefault
ownerYes
tokenNo
secondsNo
task_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is known. The description adds genuine context beyond them: exclusivity ('single writer') and the hard rule that an expired token can never write. It does not disclose the destructive consequences the annotation implies (does claiming revoke an existing holder's lease?) or what failure looks like, leaving a meaningful gap.

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?

Two short sentences, front-loaded with the action and followed by the key constraint; there is no filler. The terseness edges toward under-specification, but nothing written is wasted.

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?

The output schema covers return values, so that is not a gap. But this is a concurrency-control, destructive, non-idempotent operation whose lease duration, conflict behavior, failure mode, and four parameters are all left undescribed — the definition is thin relative to the complexity it governs.

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 four parameters, so the description must carry the burden and largely doesn't. It hints at 'token' only through the phrase 'expired token,' without explaining that passing an existing token is what performs a renewal, and it says nothing about task_id, owner, or seconds (the lease duration, defaulting to 300).

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?

The description names a specific verb pair and resource: 'Acquire or renew the single writer lease.' An agent can tell this is about taking exclusive write ownership of a task, and 'single writer' implicitly contrasts with the release sibling. It stops short of explicitly naming task_release or task_control as the counterpart, so it is clear rather than fully differentiating.

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?

'Acquire or renew' does distinguish two modes of use, which is real guidance beyond the name. However, it never states the prerequisites (must the caller own the task?), what to do when the claim fails, or which sibling to call to give the lease up. Usage is implied rather than stated.

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