Skip to main content
Glama

xyz MCP by CyberXYZ

get_vulnerability

Read-only

Full detail for one advisory id (CVE-..., GHSA-..., or an OSV id such as PYSEC-...): every affected package (affected_packages: package, ecosystem, ranges, fixed), the primary one's version ranges and fixed version, severity, CVSS, EPSS (probability of exploitation in 30 days), CISA KEV (exploited in the wild), references and how many packages depend on the affected one. Pass package / ecosystem to describe a specific affected package. Use it to explain an advisory to the user.

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-YYYY-NNNN, GHSA-xxxx-xxxx-xxxx or an OSV id
packageNoOptional: the affected package to describe, when the advisory covers several
ecosystemNoOptional: that package's ecosystem

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds real value by disclosing the payload: affected packages with ranges and fixed versions, severity, CVSS, EPSS 30-day exploitation probability, CISA KEV status, references, and dependent counts (including primary-package ranges when no package is specified). It omits error behavior for unknown ids and any result-size limits.

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 purpose, then the returned fields, then the parameter nuance, then the usage sentence. The field enumeration is dense but each item is informative; it is somewhat packed into a single long run-on sentence rather than separated, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only single-id lookup with three simple parameters and no output schema, the description covers what an agent needs: acceptable id formats, what the response contains, how to scope to a package, and when to reach for it. Residual gaps (unknown-id errors, truncation) are minor for this tool shape.

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%, so the baseline is 3. The description adds modest meaning beyond the schema by implying the default shape when package/ecosystem are omitted (the primary affected package's version ranges and fixed version), which is behavioral rather than a restatement of the field docs.

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 up front (full detail for one advisory id) and enumerates the accepted id formats (CVE, GHSA, OSV such as PYSEC). It does not name a sibling alternative to distinguish it from search or check_package, so it falls short of a 5 despite being unambiguous about what it returns.

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?

Gives one usage context ('Use it to explain an advisory to the user') and explains that package/ecosystem narrow the result to a specific affected package. There is no when-not guidance and no explicit routing to search or check_package for lookup-by-name or scanning use cases, so usage is implied rather than prescribed.

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