vealth

How to claim a packet and get paid

how_to_claim

Read-onlyIdempotent

Explains exactly how to claim work and what happens after. Claiming is free. Returns instructions, never performs the claim, because claiming requires the worker's own wallet signature. Pass the optional workId of the job in hand and the NEXT_CALL is prepare_claim for that job (with its 18+ and safety attestations when the claim gate asks), plus the job page where a person with no wallet can tap Claim and sign in with a passkey or email. Cost and signer: free and keyless, nothing to sign.

Input Schema

Name	Required	Description	Default
`workId`	No	Optional. The job in hand (e.g. WORK_1784530149768_4z4r6jz). With it the reply ends in the exact prepare_claim for that job; without it, in find_work.

Output Schema

Name	Required	Description	Default
`ok`	No
`tool`	No
`funded`	No
`payUsd`	No
`workId`	No
`claimId`	No
`claimable`	No
`next_call`	No
`proofRule`	No
`fulfillableBy`	No
`definitionOfDone`	No
`needs_from_caller`	No
`notClaimableReason`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedInput schema / properties / workId

Added value: +{
+  "description": "Optional. The job in hand (e.g. WORK_1784530149768_4z4r6jz). With it the reply ends in the exact prepare_claim for that job; without it, in find_work.",
+  "type": "string"
+}

Changed2 schema fields changedAug 26, 2026
- addedOutput schema / properties / claimable
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / notClaimableReason
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedAug 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "claimId": {
+      "type": "string"
+    },
+    "definitionOfDone": {
+      "type": [
+        "object",
+        "array",
+        "string",
+        "null"
+      ]
+    },
+    "fulfillableBy": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "funded": {
+      "type": "boolean"
+    },
+    "needs_from_caller": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "next_call": {
+      "type": "object"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "payUsd": {
+      "type": "number"
+    },
+    "proofRule": {
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "workId": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedAug 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: claiming is free and keyless, nothing must be signed here, the tool returns instructions only, actual claiming needs the worker's own wallet signature, and the reply may point to prepare_claim with 18+ and safety attestations when the gate requires them. It also explains the no-wallet job-page fallback.

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 purpose and constraints are front-loaded and every sentence carries useful information. The second sentence is dense and run-on, packing workId routing, attestations, and the no-wallet job page into one long clause, which slightly reduces readability.

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?

Given that this is an informational tool with an output schema, the description is complete: it explains what is returned, why it does not perform the claim, what the NEXT_CALL will be, cost/signer requirements, and the fallback for users without a wallet.

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?

The schema already documents the single optional workId at 100% coverage, including its effect on NEXT_CALL. The description reinforces that behavior but does not add new syntax, constraints, or format details beyond what the schema provides, so it meets the baseline for fully covered parameters.

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: it explains how to claim work and what happens afterward. It explicitly distinguishes itself from prepare_claim and submit_claim by saying it never performs the claim and is purely instructional.

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?

Clearly says when to use it: pass the optional workId of the job in hand, and the NEXT_CALL will be prepare_claim for that job. It also names the alternative path for someone without a wallet (job page with passkey/email), so the agent knows exactly how this routes relative to siblings.

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

All vealth tools Inspect

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

Need Help?