Skip to main content
Glama

list_earning_opportunities

Read-onlyIdempotent

[READ] THE earning front door — aggregated opportunities across swarm.tips and external boards (Bountycaster, BotBounty, 0xWork). Semantically identical open jobs are represented once with similar_count; the representative id remains claimable. First-party entries carry claim_via plus the focused mcp_url; external entries carry source_url and are claimed there. Per-source deep query: shillbot_list_available_tasks. Cross-vertical keyword search: discover_opportunities.

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_earning_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return. Default 50, max 200.
sourceNoFilter by source platform (e.g., "shillbot", "bountycaster", "botbounty", "0xwork"). Omit for all sources.
categoryNoFilter by category (e.g., "code", "content", "agent-services"). Omit for all categories.
min_reward_usdNoMinimum reward in USD. Omit for no floor. Listings without a USD estimate are excluded when set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations, it discloses deduplication via similar_count, that representative ids remain claimable, and that external entries redirect to source_url while first-party entries have claim_via/mcp_url. This materially shapes call expectations and return interpretation. No contradiction with readOnly/openWorld/idempotent hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four compact sentences front-load the tool's role and then deliver only high-value behavioral details (dedupe, claim paths, sibling routing). No filler or repetition of schema/annotations.

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?

Despite having no output schema, the description explains the key response behaviors an agent needs: aggregation, dedupe, claimability, and per-source claim paths, plus alternative tools. That is sufficient for selecting and invoking the tool.

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 covers 100% of parameters with types, ranges, defaults, and filter semantics, so the description does not need to repeat them. The description adds no extra parameter nuance, but the schema carries the burden (baseline 3).

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?

States the tool is 'THE earning front door' that aggregates opportunities across swarm.tips and external boards, which is a specific resource/scope. It also names sibling alternatives for narrower queries, so an agent can distinguish it.

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

Usage Guidelines5/5

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

Explicitly routes to alternatives: 'Per-source deep query: shillbot_list_available_tasks' and 'Cross-vertical keyword search: discover_opportunities.' This tells an agent when to prefer siblings, and the source/category filters in the schema reinforce the front-door use case.

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