vealth

The hour card for a packet

hour_card

Read-onlyIdempotent

The ONE document to read to a person before they start: what the place is and the circle every GPS fix must land inside, what to bring and what the safety notes say, the method steps in order, the proof to hand in as a checklist, what the land gets, what the worker gets and whether the pay is funded or only proposed, exactly what the record will hold about them, and the tool calls in order. Free, keyless, no wallet needed. The packet's own words are carried verbatim and never shortened. Read it to them in order rather than summarising it: the order is the order the hour runs in. Optionally in Swahili (lang: "sw"): the board's own sentences translate from a fixed dictionary, and the packet's own words translate only where a translation exists for that packet, tagged "(Kiingereza)" and counted in coverage where it does not; a safety-critical line always carries its English source on its own line too.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No	Optional, defaults to "en". "sw" reads the card in Swahili.
`workId`	Yes	The packet id, from find_work or place_status.

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 changedSep 15, 2026

addedInput schema / properties / lang

Added value: +{
+  "description": "Optional, defaults to \"en\". \"sw\" reads the card in Swahili.",
+  "enum": [
+    "en",
+    "sw"
+  ],
+  "type": "string"
+}

AddedSep 8, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already supply readOnly, idempotent, and non-destructive hints, and the description adds genuinely valuable behavior: the tool is free and keyless, packet words are carried verbatim and never shortened, and the Swahili translation behavior is carefully explained including coverage counting and the safety-line English source. No contradiction with 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?

The text is front-loaded with the purpose and a content list, and every sentence carries relevant information. However, it is a long, dense single block that would be easier to navigate if broken into paragraphs or bullets, making it heavier than strictly necessary for a two-parameter tool.

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?

With only two params, a rich output schema, and annotations already covering safety and idempotency, the description covers almost everything an agent needs: content, ordering, language mode, constraints, and usage instructions. Minor edge cases like invalid workId are not addressed, but the output schema and low parameter complexity make the description complete enough.

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 base baseline is 3, but the description goes further by spelling out what lang='sw' actually changes: translation from a fixed dictionary, conditional translation of packet words, coverage counting, and safety-line handling. This enriches the lang parameter beyond the schema's simple enum.

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 clearly identifies the hour card as a document to read to a person before they start, and enumerates its contents in detail, which differentiates it from packet retrieval and status tools. It lacks an explicit operation verb like 'returns' and does not name sibling alternatives, so it stops short of a 5.

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?

The description gives concrete usage context: read it before starting, read it in order rather than summarising, and optionally in Swahili. It does not explicitly state when not to use this tool or mention which sibling tool should be chosen instead.

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?