Skip to main content
Glama

get_kev_compliance

Read-only

Reports CISA KEV compliance for Vulnerability Response, showing KEV items fixed on time, fixed late, open overdue, and open within deadline, with group/CVE breakdowns and closure trends.

Instructions

CISA KEV (BOD 22-01) compliance from Vulnerability Response: KEV vulnerable items against each CVE's CISA due date, split into fixed on time, fixed late, open and overdue, and open within the deadline; breakdowns by assignment group and CVE, weekly closures over the window, and average days to close KEV against non-KEV items. Read-only

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_kev_compliance"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoWindow for closures and the trend (default 90)
limitNoMax overdue items to list (default 25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the trailing 'Read-only' merely restates the annotation rather than adding information. What the description does contribute beyond structured fields is the report's composition – the four KEV buckets, the two breakdown dimensions, the weekly trend, and the KEV-vs-non-KEV comparison – which is genuine behavioral content given no output schema exists. It discloses nothing about pagination, permission scoping, empty-result behavior, or how the window boundaries are interpreted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is dense and front-loaded with the key subject, and nearly every clause names a distinct metric, so there is little pure padding. However, it is delivered as a single semicolon-joined run-on sentence that is hard to parse, and the closing 'Read-only' is redundant with the readOnlyHint annotation. A short lead sentence plus a structured list of the report's sections would be easier for an agent to consume.

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 describing return values, and it does so thoroughly by enumerating the buckets, breakdowns, and derived averages an agent will receive. Combined with the annotation-supplied safety profile and fully documented parameters, an agent has enough to decide whether to call it and what it will get back. The missing piece is whether the result is a single aggregate object or a multi-section payload, and any size considerations for the overdue item list.

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%, with both parameters ('days' window and 'limit' for overdue items) already documented including their defaults, so the baseline is 3. The description adds only marginal reinforcement by mentioning 'weekly closures over the window', which loosely maps to the days parameter but supplies no format, bounds, or interaction details. It never mentions the 'limit' parameter's effect on truncating the overdue listing.

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, distinctive resource (CISA KEV / BOD 22-01 compliance from Vulnerability Response) and enumerates the exact facts returned: fixed on time, fixed late, open overdue, open within deadline, group and CVE breakdowns, weekly closures, and average days-to-close versus non-KEV. An agent can distinguish this from sibling compliance tools like get_compliance_assessment or get_license_compliance purely on the KEV-specific domain. It stops short of explicitly contrasting itself with those siblings, which keeps it at 4 rather than 5.

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

Usage Guidelines2/5

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

There is no when-to-use, when-not-to-use, or alternative-tool guidance anywhere in the description – only a statement of what data the report contains. The agent must infer from the KEV vocabulary alone that this is the reporting tool for CISA deadline compliance rather than a policy or posture lookup. No prerequisites, no mention of which systems or data must exist for it to return anything.

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

Deploy Server

Other Tools