Skip to main content
Glama

bounty_check

Before writing a patch for a GitHub 'bounty', check whether that repo has ever merged anyone's work. Returns the merged/total PR ratio, a verdict, and any trap signals in its open issues - such as instructions asking contributors to paste their system prompt, home directory or runtime into a public file. Verdicts: CLOSED-LOOP means the issues state in writing that only the issue author may submit a PR, so outside work is unclaimable no matter what is advertised; COLLECTOR means 50+ PRs and zero merges while advertising payment. Use this whenever a bounty promises money; an advertised amount costs the publisher nothing, a merge does.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "repo": "<repo>"
    },
    "name": "bounty_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesRepository as owner/name, e.g. ClankerNation/OpenAgents

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations at all, the description carries the full behavioral burden and mostly delivers: it enumerates the return payload (ratio, verdict, trap signals) and defines both verdict values (CLOSED-LOOP = only the issue author may submit; COLLECTOR = 50+ PRs and zero merges while advertising payment). It never states that the call is a read-only lookup with no side effects, nor anything about GitHub API auth or rate limits, which is the remaining gap for an unannotated tool.

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 purpose and the pre-patch timing constraint are front-loaded, and every clause carries information (trap-signal examples, verdict definitions). It is dense but a little long in the middle where the system-prompt/home-directory examples are spelled out at length rather than summarized.

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 one-parameter, no-output-schema lookup, the description covers the trigger, the returned fields, and the interpretation of each verdict, which is what an agent needs to act on the result. Auth requirements and rate-limit behavior are unaddressed, a minor omission given no annotations exist to cover them.

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 coverage is 100% and the single 'repo' parameter is fully documented in the schema with a format example (owner/name). The description adds only the concept of 'that repo' being under suspicion, no extra syntax or constraints, so the schema does the heavy lifting and the baseline 3 applies.

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 names a specific verb and resource ('check whether that repo has ever merged anyone's work') and scopes it to the pre-patch bounty decision. None of the siblings (ssl_check, dns_lookup, watch_*) do anything similar, and the stated output ('merged/total PR ratio, a verdict, and any trap signals') makes the operation unmistakable.

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

Usage Guidelines4/5

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

It gives an explicit trigger ('Before writing a patch for a GitHub bounty', 'Use this whenever a bounty promises money') plus the underlying rationale that an advertised amount costs the publisher nothing. There is no explicit when-not or named alternative tool, but the trigger condition is clear enough that an agent knows when to reach for it.

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