Skip to main content
Glama
DigiCatalyst-Systems

dep-diff-mcp

by DigiCatalyst-Systems
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Analyze multiple dependency changes in parallel

analyze_packages_bulk
Read-onlyIdempotent

Batch-analyze up to 50 package upgrades to get a unified risk report ranked by security, caution, review, likely-safe, and safe, with breaking changes and CVEs.

Instructions

Analyzes a list of package upgrades in parallel and returns a unified risk report with packages ranked by recommendation level (security > caution > review > likely-safe > safe). Use when the user provides many dependency changes from a Dependabot PR, npm outdated output, lockfile diff, or batch upgrade. Returns: total count, breakdown by semver class, total security fixes found, packages with breaking changes, and per-package details. Limit 50 packages per call (chunk larger lists).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
changesYesList of package changes to analyze

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
packagesYesPer-package results, ranked security > caution > review > likely-safe > safe
bySemverClassYesBreakdown of the batch by semver class
totalPackagesYesNumber of package changes submitted
securityFixesTotalYesTotal security advisories resolved across the whole batch
packagesWithBreakingChangesYesHow many packages had at least one breaking change

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.3.2
    • changedInput schema / properties / changes / items / properties / ecosystem / enum
      Previous value: -[
-  "npm",
-  "pypi"
-]New value: +[
+  "npm",
+  "pypi",
+  "github-actions"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "bySemverClass": {
+      "additionalProperties": false,
+      "description": "Breakdown of the batch by semver class",
+      "properties": {
+        "major": {
+          "description": "Count of major bumps",
+          "type": "number"
+        },
+        "minor": {
+          "description": "Count of minor bumps",
+          "type": "number"
+        },
+        "patch": {
+          "description": "Count of patch bumps",
+          "type": "number"
+        }
+      },
+      "required": [
+        "major",
+        "minor",
+        "patch"
+      ],
+      "type": "object"
+    },
+    "packages": {
+      "description": "Per-package results, ranked security > caution > review > likely-safe > safe",
+      "items": {
+        "anyOf": [
+          {
+            "additionalProperties": false,
+            "properties": {
+              "breakingChanges": {
+                "description": "Breaking changes extracted from release notes; empty when none were found",
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "ecosystem": {
+                "description": "Package ecosystem",
+                "enum": [
+                  "npm",
+                  "pypi",
+                  "github-actions"
+                ],
+                "type": "string"
+              },
+              "fromVersion": {
+                "description": "Version being upgraded from",
+                "type": "string"
+              },
+              "migrationLinks": {
+                "description": "Migration or upgrade guide URLs found in release notes",
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "package": {
+                "description": "Package name that was analyzed",
+                "type": "string"
+              },
+              "recommendation": {
+                "description": "Single-line verdict explaining the recommendation level",
+                "type": "string"
+              },
+              "recommendationLevel": {
+                "description": "Risk classification, used to rank packages in bulk results",
+                "enum": [
+                  "safe",
+                  "likely-safe",
+                  "review",
+                  "caution",
+                  "security"
+                ],
+                "type": "string"
+              },
+              "releaseCount": {
+                "description": "Number of GitHub releases found strictly between the two versions",
+                "type": "number"
+              },
+              "releaseExcerpts": {
+                "description": "Raw release-note excerpts, present only as a fallback when a major/minor bump yielded no breaking changes",
+                "items": {
+                  "additionalProperties": false,
+                  "properties": {
+                    "excerpt": {
+                      "description": "Short excerpt of the release notes",
+                      "type": "string"
+                    },
+                    "tag": {
+                      "description": "Release tag the excerpt came from",
+                      "type": "string"
+                    }
+                  },
+                  "required": [
+                    "tag",
+                    "excerpt"
+                  ],
+                  "type": "object"
+                },
+                "type": "array"
+              },
+              "repoUrl": {
+                "description": "Source repository URL, or null when none could be resolved",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "securityFixes": {
+                "description": "Advisories affecting fromVersion that are resolved at toVersion",
+                "items": {
+                  "additionalProperties": false,
+                  "properties": {
+                    "id": {
+                      "description": "Advisory identifier (e.g. 'GHSA-29mw-wpgm-hmr9' or a CVE)",
+                      "type": "string"
+                    },
+                    "severity": {
+                      "description": "Severity as reported by OSV (e.g. 'LOW', 'MODERATE', 'HIGH', 'CRITICAL')",
+                      "type": "string"
+                    },
+                    "summary": {
+                      "description": "One-line description of the advisory",
+                      "type": "string"
+                    }
+                  },
+                  "required": [
+                    "id",
+                    "summary",
+                    "severity"
+                  ],
+                  "type": "object"
+                },
+                "type": "array"
+              },
+              "semverClass": {
+                "description": "Semver relationship between the two versions",
+                "enum": [
+                  "major",
+                  "minor",
+                  "patch",
+                  "downgrade",
+                  "unknown"
+                ],
+                "type": "string"
+              },
+              "toVersion": {
+                "description": "Version being upgraded to",
+                "type": "string"
+              }
+            },
+            "required": [
+              "package",
+              "ecosystem",
+              "fromVersion",
+              "toVersion",
+              "semverClass",
+              "repoUrl",
+              "releaseCount",
+              "breakingChanges",
+              "securityFixes",
+              "migrationLinks",
+              "recommendation",
+              "recommendationLevel"
+            ],
+            "type": "object"
+          },
+          {
+            "additionalProperties": false,
+            "properties": {
+              "error": {
+                "description": "Why the analysis could not be completed",
+                "type": "string"
+              },
+              "package": {
+                "description": "Package name whose analysis failed",
+                "type": "string"
+              },
+              "recommendationLevel": {
+                "const": "review",
+                "description": "Always 'review' — a package that could not be analyzed cannot be cleared automatically",
+                "type": "string"
+              }
+            },
+            "required": [
+              "package",
+              "error",
+              "recommendationLevel"
+            ],
+            "type": "object"
+          }
+        ]
+      },
+      "type": "array"
+    },
+    "packagesWithBreakingChanges": {
+      "description": "How many packages had at least one breaking change",
+      "type": "number"
+    },
+    "securityFixesTotal": {
+      "description": "Total security advisories resolved across the whole batch",
+      "type": "number"
+    },
+    "totalPackages": {
+      "description": "Number of package changes submitted",
+      "type": "number"
+    }
+  },
+  "required": [
+    "totalPackages",
+    "bySemverClass",
+    "securityFixesTotal",
+    "packagesWithBreakingChanges",
+    "packages"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description is consistent with them. It adds useful behavioral context beyond the annotations by disclosing parallel execution and the 50-package limit with chunking guidance.

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 three front-loaded sentences with no filler: purpose and result first, usage triggers second, output summary and limit third. Every sentence earns its place and the structure makes the tool easy to evaluate quickly.

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?

Given the annotations covering safety, a single parameter with full schema coverage, and an output schema, the description is complete. It covers purpose, result contents, common input sources, and the chunking limit. The only minor omission is an explicit pointer to the singular sibling, but the plural focus makes that implicit.

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?

With schema description coverage at 100%, the schema already explains the single 'changes' parameter and its structure. The description reinforces the bulk nature and the 50-package limit, but it does not add new semantic detail about the parameter fields themselves, so the baseline score of 3 is appropriate.

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 clearly states a specific verb, resource, and result: it analyzes a list of package upgrades in parallel and returns a unified risk report with packages ranked by recommendation level. It distinguishes itself from the sibling analyze_package_change through its explicit plural/bulk focus, though it does not name the sibling directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use guidance by listing concrete triggers: Dependabot PR, npm outdated output, lockfile diff, or batch upgrade. It does not explicitly state when not to use it or mention the singular alternative, so it stops short of a full 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DigiCatalyst-Systems/dep-diff-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server