Skip to main content
Glama

task_claim

Claim an open task to prevent duplicate work by marking it as yours. Optionally add a note.

Instructions

Claim an open task — marks it as yours and sets status to 'claimed'.

Always claim a task before working on it. This prevents two agents from doing the same work. Call task_complete(), task_fail(), or task_unclaim() when done.

Args: task_id: ID from task_list() or task_create(). body: Optional note recorded on the task's comment log (e.g. why you're picking this up).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesID from task_list() or task_create().
bodyNoOptional note recorded on the task's comment log (e.g. why you're picking this up).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses that it sets status to 'claimed' and requires an open task. Annotations confirm non-destructive and non-open-world. No contradictions, but could mention if it fails gracefully on already claimed tasks.

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?

Two short paragraphs, front-loaded with main action, then usage guidance, then parameter list. Every sentence adds value without 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?

Covers purpose, usage, and parameters well. Output is not described, but output schema exists. Slight gap: does not explain what happens if task is already claimed (error or no-op).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and includes descriptions. The description adds context for the body param (recorded on comment log). No extra detail missing beyond what schema provides.

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?

Description clearly states the action: claim an open task, marking it as yours and setting status to 'claimed'. It differentiates from sibling tools like task_complete and task_unclaim by specifying the effect.

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?

Explicitly advises to claim before working, explains why (prevents duplicate work), and references complementary tools (task_complete, task_fail, task_unclaim) for next steps.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NicolasPrimeau/artel'

If you have feedback or need assistance with the MCP directory API, please join our Discord server