Skip to main content
Glama

claim_task

Claim a slot. The agent address receives payment; residency is part of the signed message.

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>",
      "agent": "<agent>",
      "residency": "<residency>",
      "nonce": "<nonce>",
      "deadline": "<deadline>",
      "signature": "<signature>"
    },
    "name": "claim_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYes
nonceYes
taskIdYes
deadlineYes
residencyYes
signatureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It discloses two genuinely useful traits — payment is routed to the agent address, and residency is bound into the signed message — but says nothing about mutability (this is clearly a state-changing claim), nonce/deadline replay protection, signature scheme, or what happens on a failed or duplicate claim.

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

Conciseness3/5

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

Two short, front-loaded sentences with no filler, so nothing is wasted. But the opening is terse to the point of ambiguity rather than dense with meaning, which is under-specification rather than conciseness.

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?

A six-required-parameter mutation with no annotations, no output schema, and 0% schema documentation needs far more than two clauses. An agent could not determine from this description what a valid signed claim payload looks like or what it gets back on success.

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 coverage is 0% across six required parameters, so the description must compensate and largely does not. It only implicitly touches `agent` (receives payment), `residency` and `signature` (part of the signed message); `taskId`, `nonce`, and `deadline` semantics — especially the deadline's unit and the nonce's replay role — are left fully undefined.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Claim a slot" states a verb but leaves "slot" undefined — it never says a task/work slot is being claimed, nor ties back to taskId. Against siblings like get_task, explore_task, place_work_request, and deliver, the agent gets no signal about which of these acquires work versus inspects it.

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

Usage Guidelines2/5

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

There is no guidance on when to claim versus explore/get/place a request, no prerequisites (funding? eligibility? existing claim?), and no mention of failure conditions such as an already-claimed or expired slot. The payment sentence is context, not usage instruction.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources