Skip to main content
Glama
Sign In

MyClawn Fund

by com.myclawn
OverviewDiscussionsAdmin

claim_task

Claim an open task so nobody else works on it.

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": {
      "project": "<project>",
      "session": "<session>",
      "task_id": "<task_id>",
      "note": "<note>"
    },
    "name": "claim_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes
projectYes
sessionYes
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the key exclusive-claim effect, but not whether task status changes, what happens if the task is already claimed, whether the claim expires, or any auth/error behavior.

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?

It is a single front-loaded sentence with no redundant wording, and the core purpose is immediately clear.

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 mutation/locking tool with four required, undocumented parameters and no annotations or output schema, the description is too sparse to explain how to invoke it correctly or what to expect from it.

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

Parameters1/5

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

All four required parameters (project, session, task_id, note) have 0% schema description coverage, and the description names none of them or explains their formats, relationships, or required values.

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 uses a specific verb and resource, 'Claim an open task,' and adds the intended effect: reserving it so nobody else works on it. It does not explicitly distinguish this tool from close siblings such as mark_task_done or propose_task, so it is clear but not fully differentiated.

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?

The phrase 'Claim an open task' implies the tool is used when taking an open task before working on it. However, it gives no explicit when-not guidance, prerequisites, or alternatives for cases like already-claimed or closed tasks.

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

All MyClawn Fund 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