Skip to main content
Glama

Patchfirst

CVEs for technique

cves_for_technique
Read-onlyIdempotent

Reverse ATT&CK lookup: which CVEs lead to a given technique, e.g. "which exploited CVEs give T1190 Exploit Public-Facing Application?". Sorted by Patchfirst priority. Parent ids include sub-techniques (T1059 matches T1059.004). Each hit shows the link's provenance badge and best evidence quote.

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": {
      "technique_id": "<technique_id>"
    },
    "name": "cves_for_technique"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 10, max 25.
kev_onlyNoOnly CVEs in CISA KEV (known exploited). Default false.
technique_idYesATT&CK technique id, e.g. "T1190" or "T1059.004"
include_subtechniquesNoFor a parent id, also match its sub-techniques. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine behavioral context beyond that: results are sorted by Patchfirst priority, parent ids expand to sub-techniques, and each hit carries a provenance badge plus best evidence quote — output traits the agent could not infer otherwise. It never explains what 'Patchfirst priority' actually ranks on, which keeps it from a 5.

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?

Three tight sentences, front-loaded with the purpose and the query pattern before the sorting and output details. Minor redundancy: the sub-technique sentence repeats what the include_subtechniques schema field already states, so one clause does not fully earn its place.

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 usefully characterizes the return shape (provenance badge, evidence quote, priority ordering) and covers the sub-technique matching rule. It is complete enough to call correctly, though the undefined 'Patchfirst priority' sort and the absence of any mention of kev_only/limit filtering leave a small gap.

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 all four parameters including limit and kev_only are already documented in structured data. The description restates the sub-technique expansion behavior ('T1059 matches T1059.004') that include_subtechniques already describes, adding reinforcement but no new meaning, and says nothing about limit or kev_only. 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 and resource — 'Reverse ATT&CK lookup: which CVEs lead to a given technique' — and the worked example (T1190) makes the direction of the mapping unambiguous. The word 'Reverse' implicitly distinguishes it from the sibling techniques_for_cve, so an agent can route between them without opening either schema.

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 example phrasing ('which exploited CVEs give T1190...') gives a clear context for when to reach for this tool, and the reverse-lookup framing signals the alternative direction. It stops short of explicitly naming techniques_for_cve as the tool to use for the opposite query, or stating exclusions, so it is clear but not fully prescriptive.

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