Skip to main content
Glama

Get security advisory

get_security_advisory
Read-only

The platform's advisory for one CVE: the parsed NVD/OSV record, CISA's guidance and due dates when the CVE is known-exploited, EPSS exploitation likelihood, and the organisation's own fleet exposure to it. Works for any CVE id, present in the fleet or not. Read-only.

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": "get_security_advisory"
  }
}

Input Schema

NameRequiredDescriptionDefault
cve_idYesCVE id, e.g. CVE-2025-1234.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

readOnlyHint=true is already declared, so the trailing 'Read-only' is redundant, but the description does the harder work the annotation cannot: it discloses the shape and provenance of the response (NVD/OSV parsing, CISA KEV guidance with due dates, EPSS score, organisation fleet exposure). It does not say what happens for malformed or unknown CVE ids, or whether enrichment fields are ever absent.

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 purpose and resource, followed by a compact enumeration of the payload and a one-clause scope rule. The final 'Read-only' sentence is pure redundancy against readOnlyHint and could be dropped without loss.

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 return-value burden and does so well by listing the four data sources an agent will receive, which is exactly what enables downstream reasoning about the result. What remains missing is edge behavior — invalid ids, unavailable EPSS/KEV enrichment — for an otherwise simple single-parameter lookup.

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 coverage is 100% with a single documented cve_id, so the baseline would be 3. The description adds meaning beyond the schema by establishing the domain of valid inputs — any CVE id, whether or not the fleet is affected — which is a genuine constraint on the parameter that the schema text does not convey.

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 and resource ('The platform's advisory for one CVE') and then enumerates the payload's components — NVD/OSV record, CISA guidance and due dates, EPSS likelihood, fleet exposure — which separates it from fleet-scoped siblings such as get_security_finding or list_security_findings. It stops short of naming a sibling alternative, so it is clear but not explicitly differentiated.

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?

'Works for any CVE id, present in the fleet or not' gives a real inclusion rule that an agent could not infer from the name or schema, resolving the intuition that this requires the CVE to already appear in findings. It offers no exclusions or named alternative tool for, e.g., looking up a finding by its internal id, so it falls just short of a 5.

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.