vealth

Find real work nearby

find_work

Read-onlyIdempotent

Search Vealth's public board of real ecological and community work packets. Each result includes the pay, the skill level, the exact proof that gets it approved, and a page URL. Free, no account, no wallet. Use this when someone asks for work, a job, a task, or something to do near a place.

Input Schema

TableJSON Schema

Name	Required	Description
`flag`	No	One posting flag, exact match, e.g. vsh_eligible — the packets that carry Regen Network proposal 77's terms (accepted hours pay REGEN, never a USD conversion). Omit for every flag.
`near`	No	A place in plain words: a city, neighborhood, address, or ZIP, e.g. 'Los Angeles, CA' or '90036'. Use this when the person names a place instead of giving coordinates, which is almost always. The board finds the place from the open jobs whose address names every word (so 'Los Angeles' never matches 'Los Fresnos'), then returns the jobs around it, nearest first.
`page`	No	Page number, starting at 1. The reply says when more pages exist.
`limit`	No	Max results per page, 1-25. Default 10.
`query`	No	Free text, e.g. 'storm drain' or 'tree planting'. Typo-tolerant.
`funded`	No	true = only packets a verified payment already backs (money truth; a funded packet can still be earned_credit and never promise cash — read payModel); false = only unfunded packets, where approved proof records earned credit rather than cash unless later funded. Omit for both.
`remote`	No	true = only work doable from anywhere (digital/self-verifying — what an agent with no field presence can complete); false = only placed field work. Omit for both.
`latitude`	No	Center of the search. Only if you already have real coordinates.
`radiusKm`	No	Search radius in km, used with latitude/longitude. Default 50.
`longitude`	No	Center of the search. Only if you already have real coordinates.
`skillLevel`	No	Use 'entry' for someone starting today.

Output Schema

TableJSON 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 changedOct 6, 2026

changedInput schema / properties / near / description

Previous value: -"A place in plain words: a city, neighborhood, address, or ZIP, e.g. 'Los Angeles, CA' or '90036'. Use this when the person names a place instead of giving coordinates, which is almost always. Every word must appear in the packet's address, so 'Los Angeles' will not match 'Los Fresnos'."New value: +"A place in plain words: a city, neighborhood, address, or ZIP, e.g. 'Los Angeles, CA' or '90036'. Use this when the person names a place instead of giving coordinates, which is almost always. The board finds the place from the open jobs whose address names every word (so 'Los Angeles' never matches 'Los Fresnos'), then returns the jobs around it, nearest first."

Changed1 schema field changedSep 24, 2026

addedInput schema / properties / flag

Added value: +{
+  "description": "One posting flag, exact match, e.g. vsh_eligible — the packets that carry Regen Network proposal 77's terms (accepted hours pay REGEN, never a USD conversion). Omit for every flag.",
+  "type": "string"
+}

Changed1 schema field changedAug 31, 2026

changedInput schema / properties / funded / description

Previous value: -"true = only packets a verified payment already backs (cash on approved proof); false = only unfunded (credit-or-mint) packets. Omit for both."New value: +"true = only packets a verified payment already backs (money truth; a funded packet can still be earned_credit and never promise cash — read payModel); false = only unfunded packets, where approved proof records earned credit rather than cash unless later funded. Omit for both."

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

Changed4 schema fields changedAug 18, 2026

addedInput schema / properties / funded

Added value: +{
+  "description": "true = only packets a verified payment already backs (cash on approved proof); false = only unfunded (credit-or-mint) packets. Omit for both.",
+  "type": "boolean"
+}

changedInput schema / properties / limit / description

Previous value: -"Max results, 1-25. Default 10."New value: +"Max results per page, 1-25. Default 10."

addedInput schema / properties / page

Added value: +{
+  "description": "Page number, starting at 1. The reply says when more pages exist.",
+  "type": "number"
+}

addedInput schema / properties / remote

Added value: +{
+  "description": "true = only work doable from anywhere (digital/self-verifying — what an agent with no field presence can complete); false = only placed field work. Omit for both.",
+  "type": "boolean"
+}

Changed4 schema fields changedAug 5, 2026

changedInput schema / properties / latitude / description

Previous value: -"Center of the search."New value: +"Center of the search. Only if you already have real coordinates."

changedInput schema / properties / longitude / description

Previous value: -"Center of the search."New value: +"Center of the search. Only if you already have real coordinates."

addedInput schema / properties / near

Added value: +{
+  "description": "A place in plain words: a city, neighborhood, address, or ZIP, e.g. 'Los Angeles, CA' or '90036'. Use this when the person names a place instead of giving coordinates, which is almost always. Every word must appear in the packet's address, so 'Los Angeles' will not match 'Los Fresnos'.",
+  "type": "string"
+}

changedInput schema / properties / radiusKm / description

Previous value: -"Search radius in km. Default 50."New value: +"Search radius in km, used with latitude/longitude. Default 50."

First observedAug 2, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds meaningful context beyond them: 'Free, no account, no wallet' tells the agent no auth or payment setup is required before calling. It does not cover pagination limits or rate behavior, but the output schema covers the return shape.

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?

Three sentences, front-loaded with the resource and scope, then the return contents, then the usage trigger. No filler, though the return-contents sentence partially duplicates what the output schema already conveys.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 11 fully documented parameters, an output schema, and annotations, the description supplies the missing pieces an agent needs: purpose, auth-free access, and a usage trigger. It is complete for correct invocation, with only sibling routing left implicit.

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% and every one of the 11 parameters, including nuanced ones like funded and remote, is documented in the schema itself. The description adds no filtering syntax or parameter meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource: 'Search Vealth's public board of real ecological and community work packets.' An agent can tell it apart from packet-level siblings like get_work_packet or my_work, but no sibling is named explicitly, so the differentiation is inferred rather than stated.

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

Usage Guidelines4/5

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

'Use this when someone asks for work, a job, a task, or something to do near a place' gives clear, concrete trigger phrasing across several paraphrases. It stops short of naming alternatives (e.g. when to use my_work or get_work_packet instead), so there are no explicit exclusions.

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?