Skip to main content
Glama

Patchfirst

Techniques for CVE

techniques_for_cve
Read-onlyIdempotent

What attackers do with a CVE: its MITRE ATT&CK techniques grouped by tactic in kill-chain order (Reconnaissance -> Impact). Each technique lists every supporting link with provenance badge, basis, evidence quote and report URL, strongest provenance first.

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": {
      "cve_id": "<cve_id>"
    },
    "name": "techniques_for_cve"
  }
}

Input Schema

NameRequiredDescriptionDefault
cve_idYesCVE id, e.g. "CVE-2023-4966"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent read, so the description's job is to add output behavior, and it does: techniques are grouped by tactic in kill-chain order, each lists all supporting links with badge, basis, quote and report URL, ordered strongest provenance first. It stops short of stating response size, pagination, or what happens for an unknown CVE.

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?

Two sentences, zero filler, with the core purpose front-loaded before the result-shape detail. The second sentence is dense but each clause describes a real output trait the agent would otherwise have to discover by calling.

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 and a single fully-documented parameter, the description carries the result-shape burden and does it well: grouping, ordering, per-link fields, provenance priority. Remaining gaps are edge behavior (unknown CVE, empty results) rather than anything needed to call it correctly.

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?

The sole parameter is fully documented in the schema (100% coverage, including an example CVE id format), so the description does not need to re-explain it. It adds no additional syntax or validity detail beyond the schema, making the baseline 3 appropriate.

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: it returns the MITRE ATT&CK techniques a CVE is used for, with the direction of the mapping ('what attackers do with a CVE') made explicit. The inverse sibling cves_for_technique is not named, so differentiation is implicit rather than stated, which keeps it out of the top band.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by the framing 'what attackers do with a CVE', which tells an agent to reach for this when it has a CVE and wants technique attribution. There is no explicit when-not guidance, no mention of the inverse lookup tool as an alternative, and no prerequisite or failure condition (e.g., unknown CVE id).

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.

Resources