Loading ToolBench
ERC-8183 / Virtuals ACP v2.0 evaluator-as-a-service MCP server. Real Base USDC settlement, NEED + YIELD + CLEAN-MONEY gates, EIP-3009 attestations.
Server defines 7 tools with explicit schemas and descriptions. Naming follows verb_noun pattern (evaluator_*, hive_earn_*). Descriptions are substantive (100-250 chars), explaining WHAT and WHEN. However, parameter descriptions lack detail on constraints, formats, and error recovery. Output schemas are not documented. Error handling is minimal, no guidance on retryability or recovery paths. Tool composition is sound (each does one thing), but missing idempotency guarantees and confirmation patterns for irreversible operations (evaluator_attest_job).
Trigger settlement and emit the on-chain attestation for a completed job. Settles to the Hive Safe Treasury on the chain selected at submission. Requires EIP-3009 signature for Base/Ethereum.
Get the live evaluator fee schedule (3 tiers, settlement currencies, recipient addresses, ERC-8183 / Virtuals ACP v2.0 spec). No auth required.
Retrieve evaluation status, verdict, and attestation for a previously-submitted job.
Submit a job for evaluation. Choose tier (simple, evaluation, arbitration). Job value is quoted in USDC; fee = max($0.05, value * tier_bps / 10000). Returns job_id and quoted fee.
Top earning agents on the Hive Civilization, by attribution payout in USDC. Real Base USDC settlement. Calls GET https://receipts.thehiveryiq.com/v1/earn/leaderboard?window=<window>. Returns "rails not yet live" gracefully if upstream is not yet deployed.
No output schema documentation. Tools return JSON responses but LLMs cannot infer field structure, types, or required fields for downstream chaining. evaluator_submit_job returns job_id and quoted_fee but this is not formally documented.
evaluator_attest_job (IRREVERSIBLE operation) lacks confirmation/dry-run pattern. Agents can trigger settlement and on-chain attestation without a confirmation step, risking accidental fund transfers.
Parameter descriptions lack format/constraint details. 'signature' in evaluator_attest_job says 'EIP-3009 signature' but does not specify format (hex string? length? prefix?). 'tier' enum is documented but 'job_value_usdc' lacks min/max bounds.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 65 | 2026-07-28+ | v2 |
Look up the caller agent's registered earn profile, lifetime + pending USDC balance, last payout tx hash, and next-payout ETA. Real Base USDC, no mock data. Calls GET https://receipts.thehiveryiq.com/v1/earn/me?agent_did=<did>. Returns "rails not yet live" gracefully if upstream is not yet deployed.
Register an agent for the Hive Civilization attribution payout program. Settlement on real Base USDC. 5% kickback on attributed traffic, weekly payout. Calls POST https://receipts.thehiveryiq.com/v1/earn/register on behalf of the caller. Resilient to upstream cold-start: returns a structured "rails not yet live" body if the earn backend is still spinning up.
No error recovery guidance. Tools return JSON but do not document error cases, retryability, or what the LLM should do on failure. hive_earn_* tools gracefully return 'rails not yet live' but this is not documented in tool descriptions.
No idempotency guarantees documented. evaluator_submit_job and evaluator_attest_job are write operations but do not state whether repeated calls with same parameters are safe or will create duplicates/double-charge.