Skip to main content
Glama

Patchfirst

Get vulnerability

get_vulnerability
Read-onlyIdempotent

Full Patchfirst record for one CVE: description, CVSS, EPSS, CISA KEV status, the ATT&CK techniques attackers use with it (each with provenance badge, basis, evidence quotes and report links), threat reports that name it, and the priority score with its factors. Every field carries provenance and a source URL.

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_vulnerability"
  }
}

Input Schema

NameRequiredDescriptionDefault
cve_idYesCVE id, e.g. "CVE-2024-3400"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, closed-world), so the description's added value is its account of the return payload — provenance badges, basis, evidence quotes, report links, source URLs on every field. That is genuinely useful context beyond the annotations, though it says nothing about behavior for an unknown or invalid CVE id.

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

Conciseness5/5

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

Two sentences, front-loaded with the resource and scope, followed by a single dense enumeration of what the record contains. Every clause maps to a real payload element and there is no filler.

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 must effectively stand in for it, and the enumerated field list plus the provenance/source-URL note does that job well for a one-parameter read tool. The only missing piece is edge-case behavior, such as what happens for an unrecognized CVE id.

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?

There is a single parameter with 100% schema description coverage and an example value, so the schema already carries the semantics. The description adds only the framing 'for one CVE', which restates the same constraint without contributing format or edge-case detail. Baseline 3 applies.

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 states a specific resource and scope: the full record for one CVE, then enumerates what that record contains (description, CVSS, EPSS, CISA KEV status, ATT&CK techniques, threat reports, priority score with factors). That enumeration implicitly separates it from list/search siblings, but no sibling is named, so an agent must infer the boundary.

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 only implied: 'for one CVE' signals a single-record lookup as opposed to a listing or search. There is no explicit when-to-use, when-not-to-use, or alternative named (e.g. search or list_exploited), so an agent has to reason about routing on its own.

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