projectpulse-mcp

analyze_dependencies

Read-onlyIdempotent

Identifies vulnerable package dependencies in a GitHub repository by fetching Dependabot alerts. Returns severity, package name, and state for each alert.

Instructions

Fetches Dependabot alerts for a GitHub repository to analyze vulnerable package dependencies.

Side effects: None. This is a strictly read-only operation.
Data sources: GitHub REST API (dependabot/alerts).
Auth requirements: Requires GITHUB_TOKEN with appropriate permissions (dependabot alerts are often restricted).
Rate limits: Subject to standard GitHub API limits.
Return shape: Returns a JSON array of vulnerable package dependencies including summary, severity, package_name, state, and html_url.
Usage guidelines: Use this tool ONLY to find vulnerable package dependencies (npm, pip, etc.). DO NOT use this tool for other checks:
- For static code security vulnerabilities (CodeQL), use 'analyze_code_scanning' instead.
- For a computed A-F health score grading, use 'get_health_score' instead.

Input Schema

TableJSON Schema

Name	Required	Description
`repo`	Yes	GitHub repository name (e.g., 'sdk')
`owner`	Yes	GitHub repository owner (e.g., 'modelcontextprotocol')
`severity`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`alerts`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.6.14Sep 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "alerts": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "html_url": {
+            "type": "string"
+          },
+          "package_name": {
+            "type": "string"
+          },
+          "severity": {
+            "type": "string"
+          },
+          "state": {
+            "type": "string"
+          },
+          "summary": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "summary",
+          "severity",
+          "state",
+          "html_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "alerts"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv1.1.4Sep 5, 2026

changedInput schema / properties / owner / description

Previous value: -"GitHub repository owner"New value: +"GitHub repository owner (e.g., 'modelcontextprotocol')"

changedInput schema / properties / repo / description

Previous value: -"GitHub repository name"New value: +"GitHub repository name (e.g., 'sdk')"

First observedv1.1.3Aug 30, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already include readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description goes beyond these by explicitly stating the operation is strictly read-only, describing the data source, and noting authentication requirements and rate limits. This adds valuable behavioral context without contradicting the annotations.

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 well-structured with bullet points separating side effects, data sources, auth requirements, rate limits, return shape, and usage guidelines. It provides comprehensive information without redundant or irrelevant text. Every sentence serves a clear purpose, making it efficient to parse.

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?

The description covers all necessary operational context: what the tool does, its read-only nature, data source, authentication needs, rate limits, return shape, and explicit usage boundaries against sibling tools. Even though an explicit output schema is not shown, the return shape summary is sufficient for an agent to understand what to expect.

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 descriptions cover owner and repo, but the severity parameter lacks a description; the tool description does not elaborate on how severity is used for filtering. With schema description coverage at 67%, the description should have compensated for the missing severity explanation, but it does not. The other parameters are clear from the schema, so a mid-range score is appropriate.

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?

The description clearly states that the tool fetches Dependabot alerts for a GitHub repository to analyze vulnerable package dependencies. It uses a specific verb ('Fetches') and resource ('Dependabot alerts'), and explicitly distinguishes itself from sibling tools by noting it is for package dependencies only, not for CodeQL (analyze_code_scanning) or health scores (get_health_score).

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use the tool ('Use this tool ONLY to find vulnerable package dependencies') and when not to use it, naming alternative tools for other checks. It also includes practical usage details such as required GITHUB_TOKEN permissions and rate limits, so an agent knows exactly when to invoke it.

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

Deploy Server