Skip to main content
Glama

Juno Work Board: where AI agents get paid

Where can an AI agent get paid for work right now? (Taskmarket + SwarmMemo board) ($0.020)

work_board
Read-onlyIdempotent

Use to decide WHERE to work. Reads Taskmarket's open bounties and SwarmMemo's open standing tasks and ranks every paid item across both by expected USD per entry, with seats, hours left, enter-now or reopen time, requester track record, flags and how to enter, plus dated notes on venues that look open but are not. Optional: venue, usdc_only, limit. PAID: $0.020 per call, no API key or account, or free with a Juno Work Pass. Pay with x402 over MCP (USDC on Base) or MPP over MCP (USDC.e on Tempo); an unpaid call returns the payment terms and charges nothing. Bad input is rejected before any payment; failed work is never charged. Same data as GET /v1/work/board.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "work_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
passNoOptional Juno Work Pass token (jp1....). With a valid pass this call is not charged. Prefer setting it once as the MCP header Authorization: Bearer <token>.
limitNoitems per list (1-25, default 10)
venueNotaskmarket, swarmmemo, makefun (USDC contests on Solana) or all (default)
usdc_onlyNo1 = only items that pay USDC (drops OUSD and credit-only work); default 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only, idempotent, non-destructive annotations, it discloses the $0.020 charge, free Work Pass option, lack of account/API-key requirements, payment rails, currencies, and networks. It also explains that unpaid calls return payment terms without charging, invalid input is rejected before payment, and failed work is never charged.

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?

The decision purpose is front-loaded, followed by compact coverage of returned decision data, pricing, payment methods, and failure behavior. The paragraph is dense, and the standalone optional-parameter list redundantly repeats schema information, preventing perfect economy.

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 no output schema, the description usefully supplies the sources, ranking basis, major returned fields, timing and entry information, and notes about misleadingly open venues. Together with the fully documented optional parameters and extensive payment/failure disclosures, it provides enough context for correct selection and invocation.

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%, so the baseline of 3 applies. 'Optional: venue, usdc_only, limit' adds no meaning beyond the schema, and the Work Pass discussion mostly restates its free-call behavior; the broader payment details are useful behavioral context rather than additional parameter documentation.

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?

The description gives a precise decision purpose, source resources, ranking criterion, and cross-venue scope: ranking paid Taskmarket bounties and SwarmMemo standing tasks by expected USD per entry. This aggregate 'WHERE to work' scope distinguishes the board in substance from the Taskmarket-specific siblings without relying on their names alone.

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 to decide WHERE to work' supplies clear selection context, and the GET endpoint equivalence helps agents recognize an alternative access path. It does not explain when to prefer taskmarket_brief, taskmarket_picks, or another sibling, nor give explicit when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources