Skip to main content
Glama
depsdev-mcp

depsdev-mcp

by Ankur1911

advisory

Read-onlyIdempotent

Fetches OSV vulnerability report details by ID, including title, severity, CVSS v3 score, and CVE aliases to verify package security risk.

Instructions

Details of one security advisory by its OSV id (for example GHSA-xxxx-xxxx-xxxx): title, severity, CVSS v3, aliases such as CVE ids.

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": {
      "advisory_id": "<advisory_id>"
    },
    "name": "advisory"
  }
}

Input Schema

NameRequiredDescriptionDefault
advisory_idYesOSV advisory id, e.g. GHSA-qw6h-vgh9-j6wx.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety and repeatability profile is carried by structured data. The description adds genuine value by disclosing the returned fields (severity, CVSS v3, CVE aliases), but says nothing about behavior when the id is unknown or malformed, or about response shape beyond that 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.

Conciseness5/5

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

One sentence, front-loaded with the verb and resource, then the identifier format, then the payoff fields. No filler, and every clause contributes something the agent needs.

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?

For a single-parameter read tool with full schema coverage and annotations that already cover safety, the description is nearly sufficient, and the inline enumeration of returned fields compensates for the absent output schema. Missing only edge-case behavior (unknown or ambiguous ids), which is a minor gap at this complexity.

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 single parameter is documented with its own GHSA example, so the description adds little beyond repeating a second illustrative id format. Baseline 3 is appropriate when the schema already supplies the parameter meaning.

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 names a specific resource (one security advisory), a specific access pattern (lookup by OSV id) and enumerates the payload (title, severity, CVSS v3, aliases/CVEs), so an agent can tell this is a single-record lookup rather than a package scan. It does not explicitly contrast itself with siblings like audit_package or lookup_hash, but the OSV-id scoping makes the distinction implicit.

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: the phrase 'by its OSV id' signals that the caller must already possess a known advisory identifier, which rules out discovery-style use. No alternative is named for the case where the agent wants a package's vulnerability set, and no error/not-found behavior is described, so guidance stays at the minimum-viable level.

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