Skip to main content
Glama
Sign In

Onplana

by io.github.Onplana
OverviewDiscussionsAdmin

claim_task

Idempotent

Take an exclusive execution lease on one task before working on it, so a second agent on the same board does not do the same work. Returns claimed=true with an expiry, or claimed=false naming the agent already executing it, or claimed=false when the task is already DONE (with its status and when it changed). The lease lapses on its own after 10 minutes, so a crashed agent never blocks a task permanently; call renew_task_lease about every 3 minutes while the work continues, and release_task when finished. Optional ttlMinutes sets a different lifetime. A lease does not change who the task is assigned to and does not grant any permission; use assign_task for ownership. Caller needs task.edit.any on the project, or task.edit.own on a task they are assigned or created.

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": {
      "taskId": "<taskId>"
    },
    "name": "claim_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYesTask to lease.
ttlMinutesNoLease lifetime in minutes. Defaults to 10, capped at 60.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say non-read-only, non-destructive, idempotent; the description goes far beyond with lease expiry semantics (10 minutes, self-lapsing so a crashed agent cannot block a task), all three return shapes including the already-DONE case, the fact that a lease grants no permission, and the exact permission requirements (task.edit.any / task.edit.own).

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?

Front-loads the purpose and the mutual-exclusion rationale, then layers return values, lease lifecycle, related tools, and permissions in a compact sequence. Every sentence carries distinct information; none is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry return values, and it does so completely (claimed true/false, competing agent, DONE status with change time). Combined with lifecycle, alternatives, and auth, an agent has everything needed to call this correctly.

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 coverage is 100% and the schema already documents ttlMinutes with its default of 10 and cap of 60. The description's mention that it 'sets a different lifetime' adds no syntax or constraint detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Take an exclusive execution lease on one task') with the exact scope and motivation ('so a second agent on the same board does not do the same work'). It explicitly separates itself from assign_task, which an agent might otherwise confuse with claiming work.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('before working on it'), the ongoing cadence ('call renew_task_lease about every 3 minutes'), the termination step ('release_task when finished'), and the alternative for a different need ('use assign_task for ownership'). Nothing about routing between siblings is left to inference.

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

All Onplana toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources