gmi-security-mcp

Overview Schema Source Related Servers Discussions Admin

check_osv_advisory

Scan one lockfile with the local osv-scanner to list known vulnerabilities per package, including installed version, fixed version, severity, and advisory links.

Instructions

Check one lockfile against OSV with the local osv-scanner.

Parses the lockfile locally, then runs osv-scanner on it and returns advisories as facts: id, package, installed version, fixed version, severity, summary, and link. Packages with only a version range and no exact version are reported unresolved, never given a verdict. No GMI call is made.

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": {
      "lockfile_path": "<lockfile_path>"
    },
    "name": "check_osv_advisory"
  }
}

Input Schema

Name	Required	Description	Default
`ecosystem`	No
`lockfile_path`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 10, 2026

TDQS

A3.5/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden well: it says parsing is local, the scanner runs locally, results are returned as factual advisories, unresolved version ranges get no verdict, and no GMI call is made. It omits operational details such as network access, error behavior, or permissions, which keeps it below a 5.

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?

The description is short, front-loaded, and free of redundant wording. Each sentence adds useful scope or behavior information.

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

Completeness3/5

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

An output schema exists, so the description need not fully explain return values, and its behavioral notes are useful. However, for a tool with two undocumented input parameters and no annotations, the absence of parameter semantics leaves a significant completeness gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage for two parameters, so the description should compensate but does not. It implies a lockfile input but never explains lockfile_path, and it does not mention the optional ecosystem parameter at all.

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 gives a specific verb and resource: checking one lockfile against OSV using the local osv-scanner. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as repo_scan or explain_cve.

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?

The implied usage is clear: use this to check a single lockfile against OSV. However, the description does not state when to prefer it over alternatives or when not to use it, leaving guidance at the implied level.

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

Deploy Server