Skip to main content
Glama

Find similar reports

find_similar
Read-onlyIdempotent

Find vulnerability reports similar to a given report by matching distinctive terms, revealing bug variations, bypasses of fixes, or the same pattern in other programs.

Instructions

Find reports that look like a given report (same technique, weakness or target type), using its most distinctive terms. Good for seeing variations of a bug, bypasses of a fix, or the same pattern in other programs.

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": {
      "id": "<id>"
    },
    "name": "find_similar"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesReport id (or hackerone.com URL) to start from. Must be in the archive.
limitNoResults to return (default 8).
same_categoryNoOnly reports in the same bug class (default false).

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds real value by disclosing that similarity is computed from 'most distinctive terms' rather than semantic matching, which shapes how results should be interpreted. It does not describe result ordering, result size behavior, or what happens when no similar reports exist.

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?

Two tight sentences with no filler. The core capability and its similarity basis come first, and the use cases follow, so the definition is well front-loaded.

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 three-parameter read-only lookup with no output schema, the definition covers what the tool does, how similarity is derived, and when to reach for it. The only meaningful gap is that it does not characterize the returned set (report objects? ranked?) beyond the name and title implying a list of reports.

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%, so id, limit, and same_category are already documented in the schema, establishing a baseline of 3. The description's mention of 'same technique, weakness or target type' loosely maps to the same_category flag but does not explain the parameter's effect or the limit default.

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+resource ('Find reports that look like a given report') and defines the similarity axis (same technique, weakness or target type) plus the mechanism (most distinctive terms). It implicitly distinguishes itself from search_reports by being seed-based rather than query-based, but never names that sibling, so an agent must infer the boundary.

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?

The second sentence gives concrete use cases: variations of a bug, bypasses of a fix, same pattern in other programs. That is clear when-to-use guidance. It stops short of explicit exclusions or naming an alternative tool for keyword-style lookup.

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