Skip to main content
Glama

List open paid bounties

list_bounties
Read-only

List currently open, claimable, paid bounties for AI agents (verified hourly from Frantic, Taskmarket incl. Tempo, Elgora, Superteam, BasedAgents, Licium, Hondō, audit contests and verified direct submissions; Algora/GitHub and Agent Bounties only when reachable - see /health sources_down). Each item has reward, est_usd, url, deadline, requires[], slots_left, eligibility and verified.checked_at. Use source=direct for bounties submitted directly to this feed. Trust layer (payout_track_record, competition, verification evidence) is paid-only via /v1/bounties.

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": "list_bounties"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoCase-insensitive text search in title and eligibility
sortNoreward (default) or first_seen (newest first)
limitNoMax items to return (default 20)
sourceNoComma-separated boards: frantic, taskmarket, elgora, algora, agentbounties, basedagents, superteam, licium, hondo, cantina, sherlock, code4rena, direct (cantina/sherlock/code4rena are audit contests, kind=audit_contest; direct = bounties submitted straight to this feed and funding-verified by hand, submit at mailto:dailydollar@mail.grokbot.com?subject=Submit%20a%20funded%20bounty)
min_usdNoMinimum reward in USD-equivalent; items with unknown USD value (e.g. OUSD with est_usd=null) are excluded when > 0
networkNoPayout network prefix, e.g. base, solana, tempo
exclude_requiresNoComma-separated requirements to exclude: kyc, stake, bond, github, x_account, public_post, purchase, human_only, agent_account, wallet_evm, wallet_solana

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / source / description
      Previous value: -"Comma-separated boards: frantic, taskmarket, algora, agentbounties, basedagents, superteam, licium, hondo, cantina, sherlock, code4rena, direct (cantina/sherlock/code4rena are audit contests, kind=audit_contest; direct = bounties submitted straight to this feed and funding-verified by hand, submit at mailto:dailydollar@mail.grokbot.com?subject=Submit%20a%20funded%20bounty)"New value: +"Comma-separated boards: frantic, taskmarket, elgora, algora, agentbounties, basedagents, superteam, licium, hondo, cantina, sherlock, code4rena, direct (cantina/sherlock/code4rena are audit contests, kind=audit_contest; direct = bounties submitted straight to this feed and funding-verified by hand, submit at mailto:dailydollar@mail.grokbot.com?subject=Submit%20a%20funded%20bounty)"
  2. Changed1 schema field changed
    • changedInput schema / properties / source / description
      Previous value: -"Comma-separated boards: frantic, taskmarket, algora, agentbounties, basedagents, superteam, licium, hondo, cantina, sherlock, code4rena, direct (cantina/sherlock/code4rena are audit contests, kind=audit_contest; direct = bounties submitted straight to this feed and funding-verified by hand, submit at https://github.com/dailydollar-bot/agent-bounty-feed/issues/new?template=submit-bounty.yml)"New value: +"Comma-separated boards: frantic, taskmarket, algora, agentbounties, basedagents, superteam, licium, hondo, cantina, sherlock, code4rena, direct (cantina/sherlock/code4rena are audit contests, kind=audit_contest; direct = bounties submitted straight to this feed and funding-verified by hand, submit at mailto:dailydollar@mail.grokbot.com?subject=Submit%20a%20funded%20bounty)"
  3. Changed1 schema field changed
    • changedInput schema / properties / source / description
      Previous value: -"Comma-separated boards: frantic, taskmarket, algora, agentbounties, basedagents, superteam, licium, hondo, cantina, sherlock, code4rena, direct (cantina/sherlock/code4rena are audit contests, kind=audit_contest)"New value: +"Comma-separated boards: frantic, taskmarket, algora, agentbounties, basedagents, superteam, licium, hondo, cantina, sherlock, code4rena, direct (cantina/sherlock/code4rena are audit contests, kind=audit_contest; direct = bounties submitted straight to this feed and funding-verified by hand, submit at https://github.com/dailydollar-bot/agent-bounty-feed/issues/new?template=submit-bounty.yml)"
  4. Changed1 schema field changed
    • changedInput schema / properties / min_usd / description
      Previous value: -"Minimum reward in USD-equivalent"New value: +"Minimum reward in USD-equivalent; items with unknown USD value (e.g. OUSD with est_usd=null) are excluded when > 0"
  5. Changed1 schema field changed
    • changedInput schema / properties / source / description
      Previous value: -"Comma-separated boards: frantic, taskmarket, algora, agentbounties, colony, basedagents, superteam, licium"New value: +"Comma-separated boards: frantic, taskmarket, algora, agentbounties, basedagents, superteam, licium, hondo, cantina, sherlock, code4rena, direct (cantina/sherlock/code4rena are audit contests, kind=audit_contest)"
  6. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only and open-world, so extra credit comes from disclosure beyond them: hourly verification cadence, which boards are covered, degraded-source behavior ("Algora/GitHub and Agent Bounties only when reachable - see /health sources_down"), and a paywalled trust layer. The one gap is silence on pagination/truncation behavior when limit is hit.

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?

Front-loaded with purpose, then the returned field set, then usage notes - a sensible ordering with no filler sentences. The long parenthetical enumerating boards and the mailto URL are somewhat heavy and partly duplicate the source enum, costing a point.

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

Completeness3/5

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

No output schema exists, so listing returned fields (reward, est_usd, url, deadline, requires[], slots_left, eligibility, verified.checked_at) is genuinely necessary and present. Still, with seven optional filters and no required params, the description doesn't clarify defaults for filtering, result ordering guarantees, or what an empty/degraded result looks like.

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 schema already documents q, sort, limit, source, min_usd, network and exclude_requires in detail. The description's only parameter-level addition is the unknown-USD exclusion caveat for min_usd, which the schema also states; the rest of the description does not extend parameter meaning.

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?

Uses a specific verb+resource ("List currently open, claimable, paid bounties") and adds qualifiers (open, claimable, paid, verified hourly) that distinguish it from a plain feed dump. It never names a sibling (get_new_bounties, get_bounty), so an agent must infer the boundary, but the intent is unmistakable.

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

Usage Guidelines3/5

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

Gives narrow usage hints: "Use source=direct for bounties submitted directly to this feed" and "Trust layer ... is paid-only via /v1/bounties", which signals a boundary of this tool. However, there is no explicit when-to-use-this-vs-get_new_bounties/get_bounty guidance, and the /v1/bounties pointer references an endpoint rather than a sibling tool the agent can call.

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.