Skip to main content
Glama

Rank a recon'd stack into a dig order

hunt_plan
Read-only

Turn a recon'd stack into a ranked dig-order for a pentest or bug-bounty hunt.

For each discovered component, returns its top high-risk CVEs (KEV / CISA-SSVC- active / high-EPSS first) AND its recurring_loci — the bug classes (CWE) this product family repeatedly fails at, ranked by real in-the-wild exploitation — i.e. WHERE to look first and WHAT shape to expect. Components are ordered by their most-exploitable bug (dig_rank). Grounded in exploitation data, not model guesses; lays out facts for triage/where-to-look, never a payload.

Banners go in verbatim ("OpenSSH_9.2p1 Debian-2+deb12u3", "Apache/2.4.62 (Debian)"): a Debian/Ubuntu/Alpine build adds distro_fix, and CVEs the distro already fixed in that build rank below the rest.

Args: technologies: discovered stack, e.g. ["craftcms 4.4", "nginx", "keycloak"]. per_tech: how many top CVEs to surface per component (default 4).

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": {
      "technologies": "<technologies>"
    },
    "name": "hunt_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
per_techNo
technologiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint annotation by disclosing the ranking logic (KEV, CISA-SSVC-active, high EPSS first), the dig_rank ordering, the recurring_loci output field, and the distro_fix rule that demotes already-patched CVEs. It also sets the expectation that output is factual triage material and never a payload, which is useful behavioral context with no output schema present.

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?

Front-loaded with the core transformation, then output detail, then argument guidance; every block serves a purpose. There is some redundancy between 'WHERE to look first and WHAT shape to expect' and 'triage/where-to-look', and a touch of promotional phrasing ('Grounded in exploitation data, not model guesses').

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by describing both the ranking dimensions and the returned structures (CVEs, recurring_loci, distro_fix). For a two-parameter read-only tool, an agent has enough to call it correctly and interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden, and it mostly does: technologies is explained as the discovered stack with concrete examples, and per_tech is given a meaning and default. The banner-verbatim guidance (including distro release suffixes) adds real semantics the schema cannot express, though version-format edge cases (e.g. bare 'nginx' vs 'nginx 1.24') remain lightly specified.

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 transformation: takes a recon'd stack and returns a ranked dig-order with per-component top CVEs plus recurring_loci CWE classes. Clearly distinct from siblings like check_technology (single lookup) and search_vulns (raw CVE search) because it explicitly frames the output as an ordered plan and a 'where to look' map.

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?

Implies the trigger well: it is the post-recon step for a pentest or bug-bounty hunt, and it says it produces triage facts rather than payloads. It never names an alternative tool or states when NOT to use it (e.g. for a single component, use check_technology), so it stops short of explicit routing.

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.