Skip to main content
Glama

Bounty New Programs

bounty_new_programs
Read-onlyIdempotent

Bug-bounty programs launched in the last N days, by real launch date. Currently HackerOne only, the only one of the three platforms that publishes a launched_at field without a login; Bugcrowd and YesWeHack expose no launch-date field at all (confirmed by enumerating their public endpoints), and are named, not silently merged in.

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": {
      "days": 90
    },
    "name": "bounty_new_programs"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLookback window in days (default 90).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavioral context beyond that: only HackerOne exposes a launched_at field without login, so coverage is deliberately limited and other platforms are not silently merged. It does not explain ordering, volume, or whether the 'named' platforms appear as stubs in output, leaving a little ambiguity.

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 key scope statement is front-loaded in the first clause. The second sentence is long and defensive, justifying platform coverage, but that rationale is decision-relevant rather than padding.

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 read-only tool with rich annotations and no output schema, the description covers what an agent needs: what it lists, the time filter, and the platform coverage limit. Return shape and result-volume behavior are the only gaps, and annotations plus the simple schema make those low-stakes.

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% and the single `days` parameter is already documented with its default, so the schema carries the burden. The description only reinforces that the window is measured against 'real launch date' rather than a crawl/first-seen date, which is a small semantic addition.

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?

The description opens with a specific resource and filter: 'Bug-bounty programs launched in the last N days, by real launch date.' An agent knows exactly what it returns. It does not, however, differentiate itself from the sibling bounty_programs_search or bounty_program, which likely cover overlapping territory.

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 the scope statement (use it when you want newly launched programs within a recent window), and the HackerOne-only caveat tells the agent when not to expect results. There is no explicit routing instruction such as 'use bounty_programs_search instead for older or cross-platform programs,' leaving the choice to inference.

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.