Skip to main content
Glama

Bounty Programs Search

bounty_programs_search
Read-onlyIdempotent

Search public bug-bounty program directories on Bugcrowd, YesWeHack and HackerOne, program name, cash bounty range, and status (open/paused/disabled), each sourced from that platform's own public, unauthenticated directory. has_wildcard checks real scope asset identifiers on YesWeHack and HackerOne (Bugcrowd's scope is behind a researcher login and is reported as such, not silently empty).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 10,
      "platform": "yeswehack",
      "min_bounty": 1000
    },
    "name": "bounty_programs_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (default 50, max 200).
queryNoCase-insensitive substring match on the program name.
platformNoRestrict to one platform. Omit to search all three.
min_bountyNoOnly programs whose published max bounty (USD) is at least this.
has_wildcardNoOnly programs whose scope includes a wildcard asset ("*.example.com"). Checked via a per-program detail call on yeswehack/hackerone; unavailable for bugcrowd (login-walled).
launched_sinceNoISO date. Only programs with a known launch date on/after this (currently HackerOne only, see bounty_new_programs note).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / launched_since / description
      Previous value: -"ISO date. Only programs with a known launch date on/after this (currently HackerOne only — see bounty_new_programs note)."New value: +"ISO date. Only programs with a known launch date on/after this (currently HackerOne only, see bounty_new_programs note)."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description does add genuinely useful context: sources are public and unauthenticated, and Bugcrowd scope is login-walled and reported as such rather than silently empty. That partial-data disclosure is the main value-add, but return format and pagination behavior remain unstated.

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?

Two sentences, front-loaded with the core action and sources, with no filler. The second sentence is dense and slightly run-on but every clause carries information.

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?

With no output schema, the description compensates by naming the returned fields (program name, bounty range, status) and flagging the Bugcrowd scope limitation. For a six-parameter, all-optional search tool this is close to complete, though pagination and result ordering are unaddressed.

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 every parameter is already documented, establishing a baseline of 3. The description restates the has_wildcard behavior and platform sourcing but adds no syntax or format detail beyond the schema.

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 verb (Search) and resource (public bug-bounty program directories on Bugcrowd, YesWeHack, HackerOne) plus the fields returned (name, cash bounty range, status). It does not explicitly differentiate itself from the sibling bounty_new_programs, which is only referenced inside the schema, so it falls short of a 5.

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 is implied by 'Search public ... directories' and the unauthenticated framing, but there is no explicit when-to-use/when-not guidance and no named alternative for the adjacent new-programs or single-program tools. The agent must infer the selection criteria.

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.