Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

tool_bounty_radar

[x402 paid: $0.002 USDC on Base] Live GitHub bounty feed: newest funded issues with repo, link and age, refreshed at call time. For agents hunting paid tasks. tools/call returns the live payment challenge.

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

Input Schema

NameRequiredDescriptionDefault
limitNoexample: 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description does real work: it discloses that the call is paid via x402 at $0.002 USDC on Base, that data is refreshed at call time, and that tools/call returns a live payment challenge rather than data. What is missing is the mechanics after the challenge—whether payment must be settled before results return, and any rate limit or failure mode.

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 short clauses, front-loaded with the price tag and payment mechanism so the agent sees the cost before the value proposition. Every sentence carries information: cost, contents, freshness, and payment flow.

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 zero-required-parameter read tool with no annotations and no output schema, the definition covers cost, payment flow, freshness, and returned fields. The main gap is the 'limit' parameter's default and maximum, plus post-payment error behavior.

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?

The single 'limit' parameter is technically covered at 100%, but the schema only says 'example: 10' with no default, maximum, or behavior when omitted, and the description never mentions it. Per the high-coverage baseline this stays at 3, though the description adds nothing on this dimension.

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 a specific verb and resource: a live feed of the newest funded GitHub bounty issues, including the returned fields (repo, link, age). No sibling tool offers bounty data, so an agent can immediately tell this apart from the price, news, or token tools.

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?

'For agents hunting paid tasks' gives an audience-level hint about when the tool is relevant, but there is no explicit when-not guidance, no named alternative, and no statement of what to do instead if the agent cannot pay. Usage is implied rather than directed.

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