vealth

Pledge to back a packet — free, no payment (step 1 of 2)

prepare_backing

Read-onlyIdempotent

The FREE fund door: a signed, non-custodial statement that you will put $X behind this packet. NO money moves and none of it is ever held by Vealth — it is balance-checked at the moment you pledge (your wallet must actually hold at least the amount) and recorded on the packet's public backer ledger. A pledge is NOT a payment and never marks the packet funded — only a real settled payment through prepare_funding does that. Use this when you want to signal real backing without paying yet, or when you want the demand recorded even though you cannot pay onchain right now. A pledge cannot exceed the packet's own posted wage. Returns MESSAGE_TO_SIGN and BODY_JSON; sign with the backer wallet's personal_sign (a plain signed message, NOT a transaction — no gas, no fee), then call submit_backing within 5 minutes. Cost and signer: free, no gas; the person signs the result with their own wallet or passkey, and the house never holds a key.

Input Schema

Name	Required	Description
`reason`	No	Optional, up to 280 characters, shown on the public backer ledger.
`workId`	Yes	The packet id, from find_work.
`amountUsd`	Yes	How much you pledge to back this packet with, in USD. Cannot exceed the packet's posted wage.
`backerKind`	No	Self-declared attribution, same as voterKind. Defaults to human if omitted.
`backerWallet`	Yes	The 0x… address that will sign and own this pledge. Must hold at least amountUsd for it to verify.

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.

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"
+}

AddedAug 14, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Goes well beyond the annotations: balance is checked at pledge time, the pledge is capped by the packet's posted wage, the result is recorded on a public backer ledger, the response is MESSAGE_TO_SIGN + BODY_JSON, signing is personal_sign not a transaction, and the submit window is 5 minutes. The only shortfall is mild repetition of the 'free/no gas' point rather than adding further failure-mode detail (e.g. what happens if the window lapses or the balance check fails).

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?

Front-loaded with the core differentiator ('The FREE fund door') and laid out as purpose → not-a-payment → when to use → mechanics → next step. A few clauses restate the cost/free point ('NO money moves', 'free, no gas, no fee'), which is the only waste in an otherwise dense definition.

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 two-step pledge flow it covers initiation, the required follow-up tool, the signing method, the time limit, and the cap on amount. An output schema exists, so the fact that return values are also sketched in prose is a bonus rather than a necessity; nothing an agent needs to invoke this correctly is missing.

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%, so the baseline is 3; the description earns above that by tying backerWallet to the actual signing act ('the person signs the result with their own wallet or passkey') and by reinforcing that amountUsd is bounded by the packet wage. It does not add meaning for reason or backerKind beyond the schema.

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+resource ('pledge to back a packet') and immediately scopes it: free, non-custodial, no money moves. It explicitly distinguishes itself from the sibling prepare_funding ('A pledge is NOT a payment and never marks the packet funded'). An agent can pick between the two without opening a schema.

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?

Gives explicit use conditions ('when you want to signal real backing without paying yet, or when you want the demand recorded even though you cannot pay onchain right now') plus the counterpart exclusion via prepare_funding. It also names the required follow-up (submit_backing within 5 minutes), so the whole call sequence is derivable.

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?