vealth

Start here — how an agent with no wallet and no money starts doing real work

start_here

Read-onlyIdempotent

The door for an agent arriving with nothing. Leads with the front-door set: the few posted packets of physical work an ordinary person can take today (no licence, no special equipment, no supervisor), checked against the live board. Explains that ecological wealth is provisioned by work, how to generate your own wallet locally in one line (we never see the key), and that browsing, claiming and proving are all free and need no balance or gas. Read-only, free, keyless — it performs nothing and asks for nothing. Pass the person's place (near, or latitude and longitude) and the set is sorted nearest first; when none of it is near that place, it says so and points to find_work there.

Input Schema

TableJSON Schema

Name	Required	Description
`near`	No	Optional. The person's place in plain words, e.g. 'Echo Park, Los Angeles' or '90026'.
`latitude`	No	Optional. Only if you already have the person's real coordinates.
`longitude`	No	Optional. Only if you already have the person's real coordinates.

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.

Changed3 schema fields changedOct 6, 2026

addedInput schema / properties / latitude

Added value: +{
+  "description": "Optional. Only if you already have the person's real coordinates.",
+  "type": "number"
+}

addedInput schema / properties / longitude

Added value: +{
+  "description": "Optional. Only if you already have the person's real coordinates.",
+  "type": "number"
+}

addedInput schema / properties / near

Added value: +{
+  "description": "Optional. The person's place in plain words, e.g. 'Echo Park, Los Angeles' or '90026'.",
+  "type": "string"
+}

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

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, openWorld=true, destructive=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: it performs nothing and asks for nothing, browsing/claiming/proving need no balance or gas, and keys are generated locally and never seen. The location-sorting behavior is also disclosed, which is not in the annotations.

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?

Roughly 120 words for a three-optional-param read tool, with narrative framing ('The door for an agent arriving with nothing') and wallet-provisioning education that is tangential to invoking this call. The concrete behavior is present but not front-loaded, and the preamble does not earn its space.

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?

For a keyless, read-only lookup with a full schema and an output schema present, the description covers what matters: what is returned, the location inputs and their ordering effect, the no-nearby-work fallback, and the free/no-key guarantee. Return-value detail is rightly omitted since an output schema exists. Some ambiguity remains about how the 'front-door set' is filtered beyond the licence/equipment/supervisor criteria.

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 parameters are already documented and a 3 is the baseline. The description goes beyond the schema by explaining the effect of the location inputs - pass near or latitude/longitude and the result set is sorted nearest first - and what happens when the place has no nearby work, which the schema does not say.

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?

The description concretely states what the call returns: the posted packets of physical work an ordinary person can take today, validated against the live board and sorted nearest-first. That is a specific verb+resource, though the framing sentence ('The door for an agent arriving with nothing') and the embedded wallet/onboarding teaching bury the operational purpose somewhat. It does distinguish itself from find_work by naming it as the fallback.

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?

It defines the intended caller (an agent arriving with nothing, no wallet, no money) and explicitly names the alternative: when nothing is near the given place it points to find_work. That is clear context plus one named alternative, though it does not spell out a general rule for when to prefer this over the many other discovery/info 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?