BugSecure MCP

Get the researcher leaderboard

get_leaderboard

Read-onlyIdempotent

Fetch BugSecure researcher rankings by reputation or validated reports, filter by country, and view ranked profiles for a chosen period.

Instructions

Top researchers on BugSecure. All-time ranks by reputation; monthly/quarterly rank by reports validated in that period. Optionally filtered by country code. Use get_researcher_profile with a username for more about one researcher.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	How many researchers (1–100).
`period`	No	Ranking period: all_time (reputation), monthly or quarterly (validated reports).	all_time
`country`	No	Only researchers whose profile country is this ISO 3166-1 alpha-2 code (SN, CI, FR…).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`period`	No
`researchers`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.2.2Oct 3, 2026

changedInput schema / properties / country / description

Previous value: -"Only researchers whose profile lists this country, exactly as written on their profile."New value: +"Only researchers whose profile country is this ISO 3166-1 alpha-2 code (SN, CI, FR…)."

removedInput schema / properties / country / maxLength
```
Removed value: -100
```
removedInput schema / properties / country / minLength
```
Removed value: -1
```
addedInput schema / properties / country / pattern
```
Added value: +"^[A-Za-z]{2}$"
```

First observedv0.1.0Sep 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuine value beyond that: it explains what the ranking is computed from for each period, which the annotations cannot convey. It omits sort order and return shape, but an output schema exists.

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 compact sentences, front-loaded with the core purpose, then period semantics, then the alternative-tool routing. No redundant or filler content.

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 annotations covering safety, a full input schema, and an output schema present, the description supplies all an agent needs to select and call it. Minor gap: no mention of result ordering or default-limit implications, but these are handled by schema defaults.

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% with a documented enum for period, default, and country pattern, so the schema carries the parameter burden. The description largely restates the schema's period semantics rather than adding new meaning. Baseline 3 is appropriate.

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+resource (top researchers leaderboard on BugSecure) and immediately differentiates from the sibling get_researcher_profile by naming it as the single-researcher alternative. An agent can tell exactly what this returns.

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?

Explains when each period mode applies (all_time = reputation, monthly/quarterly = validated reports) and routes to get_researcher_profile for per-user detail. No explicit 'when not to use' or exclusions, but the context is clear.

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