Skip to main content
Glama

Program profile

get_program
Read-onlyIdempotent

Profiles a HackerOne program's disclosed reports, severity mix, common bug classes, bounties, and upvoted/recent findings to help assess a target's history before testing.

Instructions

Profile of one HackerOne program in the archive: disclosed report count, severity mix, the bug classes it gets most, bounties, its most upvoted and latest disclosed reports. Useful to understand a target's history before testing it.

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": {
      "program": "<program>"
    },
    "name": "get_program"
  }
}

Input Schema

NameRequiredDescriptionDefault
programYesProgram handle or name, e.g. "gitlab", "shopify", "uber".
examplesNoHow many reports to list in each section (default 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description's added value is enumerating what the result contains — important since there is no output schema — but it adds nothing about scoping limits, error behavior for an unknown program handle, or the per-section cap of 20.

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?

A single front-loaded sentence: what the tool returns first, the section list second, the use case last. Every clause earns its place, and the enumerations substitute for a missing output schema 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?

With no output schema, the description carries the burden of explaining return contents and does so thoroughly. Gaps remain around lookup failure behavior and how the examples parameter interacts with each section, but nothing essential to correct invocation is missing.

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 both parameters (program handle/name, examples count with default 5) are already fully documented, including the example formats and the 0–20 bounds. The description adds no meaning beyond the schema, so the baseline 3 applies.

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 names a specific verb+resource ('Profile of one HackerOne program in the archive') and enumerates the profile contents (report count, severity mix, bug classes, bounties, upvoted/latest reports), which makes it clearly distinct from aggregate siblings like archive_stats or single-item siblings like get_report. It stops short of explicitly naming an alternative, so a 4 rather than 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 Guidelines4/5

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

It gives concrete usage context: 'Useful to understand a target's history before testing it.' That tells the agent when this tool fits. It does not state exclusions or point to sibling tools for narrower questions, which keeps it below a 5.

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