BugSecure MCP

Search bug bounty programmes

search_programs

Read-onlyIdempotent

Find active bug bounty programmes by free-text query, organization, or reward range. Returns paginated summaries; use get_program for full scope and rules.

Instructions

Search the public BugSecure catalogue of active bug bounty programmes. Filter by free-text query, organization or reward range; results are paginated with limit/offset. Returns summaries only — call get_program with an id for scope, rules and the reward grid. invited: true lists instead the private programmes the user was invited to.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Results per page (1–50).
`query`	No	Free-text search over programme titles and descriptions.
`offset`	No	Results to skip.
`invited`	No	List the private programmes you were invited to (no other filter applies).
`maxReward`	No	Only programmes whose reward grid pays at most this much.
`minReward`	No	Only programmes whose reward grid pays at least this much.
`organizationId`	No	Only programmes run by this organisation.

Output Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`offset`	No
`programs`	No
`nextOffset`	No	Next page’s `offset`; null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 25, 2026

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 destructiveHint false, so the safety profile is known. The description adds behavioral context by noting it returns summaries only and that invited:true switches to private programmes, which is beyond the annotations. No contradiction with 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?

The description is two well-structured sentences. The main purpose is front-loaded, followed by key filtering and pagination details, then the invited-mode distinction. No wasted words, and all information 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?

Given the output schema exists and the annotations cover safety, the description adequately covers the tool's behavior: filtering, pagination, summary-only returns, and the invited mode. It doesn't mention sorting order or edge cases, but these are minor for a read-only search tool with 100% schema coverage.

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%, with each of the 7 parameters documented. The tool description adds little semantic value beyond rephrasing the schema, e.g., 'filter by free-text query, organization or reward range' simply summarizes the existing parameter descriptions. 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 clearly identifies the tool as searching the public BugSecure catalogue of active bug bounty programmes, with explicit filtering options and pagination. It distinguishes itself from get_program, which retrieves detailed scope/rules, making the purpose 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?

The description explicitly states that results are summaries and directs the user to get_program for full details, establishing clear when-to-use guidance. It also clarifies the special invited:true mode, giving an explicit alternative context without ambiguity.

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