Skip to main content
Glama

Base Agent Due-Diligence Kit

Base USDC Earn Radar ($0.010)

earn_radar
Read-onlyIdempotent

AI-researched, source-linked, dated list of bounties, grants, audit contests and x402 revenue channels that pay USDC on Base, plus an avoid-list (boards that did not pay, AI-forbidden programs). Each entry: payout, deadline, claim rules, agent policy, payout evidence, sources, confidence. PAID: $0.010 per call in USDC on Base via x402, or use a 0.25 USDC transfer pass (pay_tx). See payment_options. By Juno.

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

Input Schema

NameRequiredDescriptionDefault
kindNocomma list: bounty, grant, audit-competition, revenue-channel, bounty-board, hackathon, investment, rewards
skillNosubstring match on skills, e.g. research, solidity, content
pay_txNoOptional, for the plain-transfer option (no x402 needed): hash of a USDC transfer of >= 0.25 USDC to this server's receiving address (get it from the payment_options tool). One transfer unlocks every paid tool for 24h.
statusNocomma list of: open, open-unverified, rolling, upcoming, closed, avoid, not-revenue
min_usdNominimum payout in USD
agent_okNo1 = drop entries whose agent policy forbids AI agents
pay_chainNoChain of pay_tx (default: inferred; 0x hash = base, base58 signature = solana)
actionableNo1 = only open / open-unverified / rolling entries

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, and the description adds the critical behavior they cannot express: this is a metered tool that costs $0.010 per call or requires a prepaid 0.25 USDC transfer pass. It also discloses the per-entry payload (payout, deadline, claim rules, agent policy, payout evidence, sources, confidence) and notes some boards are excluded as non-paying or AI-forbidden. It stops short of saying whether failed or empty calls are still billed, or how large the result set is.

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 definition is front-loaded with what the tool returns and packs provenance, entry fields, pricing and payment mechanics into three efficient sentences with no filler. The pricing/payment clause is dense but each element carries information an agent needs before calling.

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?

For a read-only discovery tool with no output schema, the description supplies what would otherwise be missing: the shape of each entry and the provenance/confidence metadata, plus the full payment model and where to obtain the receiving address. Combined with a fully documented parameter schema, an agent has enough to call this correctly.

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%, and every one of the eight filters (kind, skill, status, min_usd, agent_ok, pay_tx, pay_chain, actionable) is documented in the schema itself. The description only implies filtering through its mention of an avoid-list and actionable entries; it adds no syntax or interaction guidance beyond the schema, so the baseline of 3 applies.

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?

States a specific resource (an AI-researched, source-linked, dated list of USDC-paying bounties, grants, audit contests and x402 revenue channels on Base) and adds the avoid-list dimension, so the agent knows exactly what it yields. It does not name the obvious free alternative (earn_radar_preview) even though the description stresses the paid nature, so sibling differentiation is only implied.

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?

Usage guidance is centered on the payment route: $0.010 per call via x402, or a 0.25 USDC transfer hash in pay_tx that unlocks all paid tools for 24h, with a pointer to payment_options. It never says when to pick this over the preview or the other paid researchers, and gives no guidance on which filters to combine for a typical query.

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