Skip to main content
Glama

claim supervisor task

claim_supervisor_task

Claim a pending repair task exclusively for 15 minutes using a write-scope key, preventing other supervisors from picking it up while you work.

Instructions

Claim a pending repair exclusively for 15 minutes. Keep leaseToken private. Requires a write-scope key.

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": {
      "jobId": "<jobId>"
    },
    "name": "claim_supervisor_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses an exclusive 15-minute lease, an auth prerequisite (write-scope key), and a secrecy constraint on the leaseToken. It stops short of explaining lease expiry behavior, renewal, or what happens if the repair is already claimed, which are the main behavioral gaps.

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

Conciseness5/5

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

Three short sentences, front-loaded with the core action, and each one adds a distinct constraint (exclusivity/duration, token secrecy, auth scope). No filler or redundancy.

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?

For a one-parameter mutation with no output schema and no annotations, the description covers the essential context: lease semantics, credentials, and secret handling, and it hints that a leaseToken is returned. It is only incomplete on error cases and the meaning of the required parameter.

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?

The schema has 0% description coverage for the single jobId parameter, so the description must compensate, and it does not—jobId is never mentioned or explained as the identifier of the repair to claim. The agent must guess that jobId refers to the target repair.

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 gives a specific verb and resource ('Claim a pending repair') plus the exclusivity and duration semantics that define the operation. It does not name a sibling such as release_supervisor_task or list_supervisor_queue to sharpen the boundary, so it falls short of 5.

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?

'Pending repair' implies the condition under which claiming makes sense, and the write-scope key requirement is stated as a prerequisite. However, there is no explicit guidance on what to do if the claim fails, when to prefer list_supervisor_queue first, or when release_supervisor_task is appropriate, leaving usage largely inferable.

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