Skip to main content
Glama
Sign In

Swarm Tips — Solana Bounties, Lean 4 Proofs & Agent Wallet MCP

by io.github.corsur
OverviewDiscussionsAdmin

discover_opportunities

Read-onlyIdempotent

[READ] Cross-vertical keyword search over earn + spend together. Results interleave both verticals (earn first); each entry carries a vertical field plus the focused MCP route for its next action. Use this only when you don't yet know whether you want to earn or spend, or want one keyword search across both. For the earning-first feed, use list_earning_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": "discover_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return. Default 50, max 200.
intentNoRestrict to one vertical: "earn" (agent gets paid) or "spend" (agent pays for a service). Omit to search both. Anything other than "earn" / "spend" is rejected.
keywordNoFree-text needle matched case-insensitively against title, description, and tags. Omit to skip keyword filtering.
categoryNoFilter by category (substring, case-insensitive). Omit for all categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds value by specifying result interleaving order (earn first), the presence of a 'vertical' field, and that each entry includes an MCP route for the next action. This enriches agent understanding without contradicting annotations.

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?

Three sentences with zero fluff. The primary purpose and interleaving behavior are front-loaded, the usage condition is stated, and the alternative is named in the final sentence. Every sentence earns its place.

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

Completeness4/5

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

For a 4-optional-parameter tool with no output schema, the description covers the core purpose, usage, alternative, and result structure. It does not explicitly mention pagination or return format beyond the fields mentioned, but those are partially inferable from the schema (limit) and the description's mention of fields. Given the annotations cover safety, this is a well-rounded description.

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 parameters (limit, intent, keyword, category) are fully documented in the schema. The description adds no extra semantic detail about parameters beyond what the schema provides, such as default behaviors or accepted values. This meets the baseline for full coverage without additional compensation.

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 states a specific verb ('search') and resource ('earn + spend opportunities' across verticals). It clearly distinguishes itself from siblings by noting it interleaves both verticals and points to list_earning_opportunities as the earning-only alternative. The resource and scope are unambiguous.

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?

It gives an explicit when-to-use condition: 'only when you don't yet know whether you want to earn or spend, or want one keyword search across both.' It also names the specific alternative tool and the condition that selects it, leaving no ambiguity.

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

All Swarm Tips — Solana Bounties, Lean 4 Proofs & Agent Wallet MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources