patchwork-os

getSecurityAdvisories

Read-only

Audits project dependencies for known CVEs, returning severity levels and remediation advice. Supports npm, yarn, pnpm, cargo, and pip with auto-detection.

Instructions

Security audit: CVEs with severity and remediation. Auto-detects npm/yarn/pnpm/cargo/pip-audit.

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

Input Schema

Name	Required	Description
`severity`	No	Minimum severity to include in results. Default: all
`onlyFixable`	No	Only return advisories that have a known fix available
`packageManager`	No	Package manager to audit. Default: auto-detect

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 20, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true, and the description adds context about auto-detecting package managers and providing remediation. This enhances transparency beyond annotations, though it does not detail behavior on auto-detection failure.

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?

Single sentence, front-loaded with the tool's purpose, no redundant information. Highly efficient.

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 3 parameters, no output schema, and simple boolean/enum types, the description covers the key aspects. However, it lacks a hint about the output structure (e.g., returns a list of advisories with CVE IDs), which would be helpful for a complete understanding.

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% with clear parameter descriptions. The description mentions 'severity' and 'remediation' but adds minimal new meaning beyond the schema. Baseline 3 is appropriate since schema already documents parameters well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool retrieves security advisories (CVEs) with severity and remediation, and auto-detects multiple package managers. This distinguishes it from siblings like 'auditDependencies' by specifying the output (CVEs) and the auto-detection feature.

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?

Description implies use for security audits, but does not provide explicit guidance on when to use this tool versus the closely related sibling 'auditDependencies'. No when-not-to-use or alternative hints are given.

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

Deploy Server