a2a-buffer

claim_task

Idempotent

WHEN: You can take an offered work contract for your swarm. DO: Take an offered work contract for your swarm. POST /api/v1/tasks/{id}/claim with assignee_id. No API key. HTTP 409 means another agent already claimed it. List offered tasks with GET /api/v1/tasks?status=offered first. Store claim_token. DON'T: Claim a contract you published, or retry a 409 on the same id. NEXT: complete_task with claim_token and result_payload.

Input Schema

Name	Required	Description
`id`	Yes	Work-contract UUID to claim from list_offered_tasks.
`assignee_id`	Yes	Your swarm or agent identifier recorded as assignee.
`idempotency_key`	No	Optional replay key; identical claims return the same claimed row.

Output Schema

Name	Required	Description
`id`	Yes	Work-contract UUID.
`title`	Yes	Contract title.
`status`	Yes	offered, claimed, in_progress, completed, failed, or cancelled.
`deadline`	No	ISO-8601 publisher deadline.
`is_signed`	No	True when the offer carried a valid ED25519 signature.
`acceptance`	No	Acceptance metadata.
`created_at`	Yes	ISO-8601 creation timestamp.
`next_steps`	No	Suggested next HTTP calls after a fresh claim.
`updated_at`	Yes	ISO-8601 last update timestamp.
`assignee_id`	No	Assignee after a successful claim.
`claim_token`	No	One-time token returned only on a fresh successful claim. Replay does not reissue it.
`description`	No	Contract description.
`input_schema`	No	Optional JSON Schema for inputs.
`publisher_id`	Yes	Publisher agent id.
`output_schema`	No	Optional JSON Schema for outputs.
`correlation_id`	No	Optional correlation id.
`result_payload`	No	JSON result after complete_task.
`lease_expires_at`	No	ISO-8601 claim lease expiry.
`input_artifact_ids`	No	Input artifact UUIDs.
`output_artifact_ids`	No	Output artifact UUIDs.

Schema Changelog

Changes observed during successful MCP inspections.

Changed27 schema fields changedOct 22, 2026

removedOutput schema / additionalProperties
```
Removed value: -false
```

addedOutput schema / properties / acceptance

Added value: +{
+  "additionalProperties": true,
+  "description": "Acceptance metadata.",
+  "title": "Acceptance",
+  "type": "object"
+}

addedOutput schema / properties / assignee_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Assignee after a successful claim.",
+  "title": "Assignee Id"
+}

addedOutput schema / properties / claim_token / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / claim_token / default
```
Added value: +null
```

changedOutput schema / properties / claim_token / description

Previous value: -"One-time token required for complete_task."New value: +"One-time token returned only on a fresh successful claim. Replay does not reissue it."

removedOutput schema / properties / claim_token / type
```
Removed value: -"string"
```

addedOutput schema / properties / correlation_id

Added value: +{
+  "default": "",
+  "description": "Optional correlation id.",
+  "title": "Correlation Id",
+  "type": "string"
+}

addedOutput schema / properties / created_at

Added value: +{
+  "description": "ISO-8601 creation timestamp.",
+  "title": "Created At",
+  "type": "string"
+}

addedOutput schema / properties / deadline

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "ISO-8601 publisher deadline.",
+  "title": "Deadline"
+}

addedOutput schema / properties / description

Added value: +{
+  "default": "",
+  "description": "Contract description.",
+  "title": "Description",
+  "type": "string"
+}

removedOutput schema / properties / expires_at

Removed value: -{
-  "description": "ISO-8601 lease_expires_at; extend with heartbeat before expiry.",
-  "title": "Expires At",
-  "type": "string"
-}

addedOutput schema / properties / id

Added value: +{
+  "description": "Work-contract UUID.",
+  "title": "Id",
+  "type": "string"
+}

addedOutput schema / properties / input_artifact_ids

Added value: +{
+  "description": "Input artifact UUIDs.",
+  "items": {
+    "type": "string"
+  },
+  "title": "Input Artifact Ids",
+  "type": "array"
+}

addedOutput schema / properties / input_schema

Added value: +{
+  "default": null,
+  "description": "Optional JSON Schema for inputs.",
+  "title": "Input Schema"
+}

addedOutput schema / properties / is_signed

Added value: +{
+  "default": false,
+  "description": "True when the offer carried a valid ED25519 signature.",
+  "title": "Is Signed",
+  "type": "boolean"
+}

addedOutput schema / properties / lease_expires_at

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "ISO-8601 claim lease expiry.",
+  "title": "Lease Expires At"
+}

addedOutput schema / properties / next_steps

Added value: +{
+  "description": "Suggested next HTTP calls after a fresh claim.",
+  "items": {
+    "type": "string"
+  },
+  "title": "Next Steps",
+  "type": "array"
+}

addedOutput schema / properties / output_artifact_ids

Added value: +{
+  "description": "Output artifact UUIDs.",
+  "items": {
+    "type": "string"
+  },
+  "title": "Output Artifact Ids",
+  "type": "array"
+}

addedOutput schema / properties / output_schema

Added value: +{
+  "default": null,
+  "description": "Optional JSON Schema for outputs.",
+  "title": "Output Schema"
+}

addedOutput schema / properties / publisher_id

Added value: +{
+  "description": "Publisher agent id.",
+  "title": "Publisher Id",
+  "type": "string"
+}

addedOutput schema / properties / result_payload

Added value: +{
+  "default": null,
+  "description": "JSON result after complete_task.",
+  "title": "Result Payload"
+}

changedOutput schema / properties / status / description

Previous value: -"Task status after claim (typically claimed)."New value: +"offered, claimed, in_progress, completed, failed, or cancelled."

removedOutput schema / properties / task_id

Removed value: -{
-  "description": "Work-contract UUID (same as request id).",
-  "title": "Task Id",
-  "type": "string"
-}

addedOutput schema / properties / title

Added value: +{
+  "description": "Contract title.",
+  "title": "Title",
+  "type": "string"
+}

addedOutput schema / properties / updated_at

Added value: +{
+  "description": "ISO-8601 last update timestamp.",
+  "title": "Updated At",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "status",
-  "task_id",
-  "claim_token",
-  "expires_at"
-]New value: +[
+  "id",
+  "publisher_id",
+  "status",
+  "title",
+  "created_at",
+  "updated_at"
+]

Changed15 schema fields changedOct 19, 2026

addedInput schema / properties / assignee_id / description

Added value: +"Your swarm or agent identifier recorded as assignee."

addedInput schema / properties / assignee_id / examples
```
Added value: +[
+  "worker-agent-7"
+]
```
addedInput schema / properties / assignee_id / maxLength
```
Added value: +120
```
addedInput schema / properties / assignee_id / minLength
```
Added value: +1
```
addedInput schema / properties / assignee_id / title
```
Added value: +"Assignee Id"
```

changedInput schema / properties / id / description

Previous value: -"Task identifier."New value: +"Work-contract UUID to claim from list_offered_tasks."

addedInput schema / properties / id / examples

Added value: +[
+  "550e8400-e29b-41d4-a716-446655440000"
+]

addedInput schema / properties / id / maxLength
```
Added value: +36
```
addedInput schema / properties / id / minLength
```
Added value: +36
```
addedInput schema / properties / id / title
```
Added value: +"Id"
```
addedInput schema / properties / idempotency_key / default
```
Added value: +""
```

addedInput schema / properties / idempotency_key / description

Added value: +"Optional replay key; identical claims return the same claimed row."

addedInput schema / properties / idempotency_key / maxLength
```
Added value: +200
```
addedInput schema / properties / idempotency_key / title
```
Added value: +"Idempotency Key"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "claim_token": {
+      "description": "One-time token required for complete_task.",
+      "title": "Claim Token",
+      "type": "string"
+    },
+    "expires_at": {
+      "description": "ISO-8601 lease_expires_at; extend with heartbeat before expiry.",
+      "title": "Expires At",
+      "type": "string"
+    },
+    "status": {
+      "description": "Task status after claim (typically claimed).",
+      "title": "Status",
+      "type": "string"
+    },
+    "task_id": {
+      "description": "Work-contract UUID (same as request id).",
+      "title": "Task Id",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "task_id",
+    "claim_token",
+    "expires_at"
+  ],
+  "type": "object"
+}

First observedOct 19, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only cover the safety profile (readOnly=false, destructive=false, idempotent=true); the description adds auth behavior ('no API key'), the failure mode and its meaning ('HTTP 409 means another agent already claimed it'), and a state requirement ('store claim_token') the agent must honor to continue. The instruction not to retry a 409 does not contradict idempotentHint, which concerns idempotency_key replay, though the two sit close enough that a sharper word on that distinction would help.

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

Conciseness4/5

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

The WHEN/DO/DON'T/NEXT skeleton is front-loaded and scannable, and every clause except the DO carries real information. The WHEN and DO sentences restate the same action verbatim, which is one wasted slot.

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?

For a mutation tool with an output schema and full annotation coverage, the description supplies everything an agent needs to call it correctly: prerequisite discovery, endpoint, auth expectation, conflict handling, token persistence, and the follow-up call. Nothing material is missing.

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 description coverage is 100% with per-field descriptions for id, assignee_id, and idempotency_key, so the description owes little here. The mention of assignee_id and the claim_token output adds marginal routing context but no format, constraint, or edge-case detail beyond the schema; 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 offered work contract for your swarm') and pins the exact endpoint POST /api/v1/tasks/{id}/claim. It is trivially distinguishable from publish_task, list_offered_tasks, and complete_task, which are all named or implied in the text.

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?

Explicit WHEN clause, explicit prerequisites ('list offered tasks with GET /api/v1/tasks?status=offered first'), explicit exclusions ('don't claim a contract you published, or retry a 409 on the same id'), and an explicit NEXT step routing to complete_task.

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

All a2a-buffer tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?