Skip to main content
Glama

Fencer Intel vulnerability feed

Get one vulnerability

get_vulnerability

Full entry for a CVE, GHSA or OSV id: description, CVSS, CISA KEV status and due date, EPSS score and the date it first reached 10%, public exploits (Exploit-DB, Metasploit), affected packages with fixed versions, affected products, references and source records; where known, ATT&CK techniques (attack), ransomware groups (ransomware) and the Project Zero zero-day listing (zeroDay); vendorAdvisories holds vendor CSAF advisories and VEX statements (CISA, Red Hat): per product affected, fixed or not affected, with the remediation and a link (keep the credit of each with it); maintainerAdvisory links the advisory the maintainers published on their GitHub repository and says whether it is unreviewed (GitHub has not reviewed it yet, so the affected packages and versions are the maintainers’ word); inferredPackages (only when no record lists packages) are npm or PyPI packages inferred because a CVE product has the package’s name and the CVE references the GitHub repository the package’s registry entry names: low confidence, say "probably" and that no advisory lists them.

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": {
      "id": "<id>"
    },
    "name": "get_vulnerability"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCVE-…, GHSA-… or an OSV id (PYSEC-…, GO-…, RUSTSEC-…).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; it is silent on read-only semantics, error behavior and rate limits, but it does disclose real behavioral nuance — that maintainerAdvisory may be unreviewed and that inferredPackages are low-confidence inferences only present when no record lists packages. That provenance and confidence guidance is genuinely valuable beyond the field list.

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

Conciseness2/5

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

One enormous run-on sentence with semicolon-chained clauses; the second half (vendorAdvisories, maintainerAdvisory, inferredPackages) is a wall of text where a list would be far more scannable. It is front-loaded with the headline fields, but the size and lack of structure hurt comprehension.

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 explain return contents and does so thoroughly, including field provenance, vendor CSAF/VEX semantics and the credit-retention note. What is missing is usage context rather than return-value coverage.

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% and the id parameter already documents the accepted id families. The description repeats the same CVE/GHSA/OSV enumeration without adding format examples or constraints beyond the schema, so 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 opening clause states a specific resource and scope: a full single-record entry keyed by a CVE, GHSA or OSV id, followed by an enumeration of the fields it returns. The implicit contrast with 'search' and 'list_feed' is only suggested by 'Full entry ... for a CVE id' — no sibling is named, so the differentiator must be inferred.

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 statement of when to use this versus search, check_stack or list_feed, and no mention of prerequisites such as a valid id or what happens on a miss. An agent must derive usage from the description's shape alone.

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