Skip to main content
Glama
Sign In
Documentation Search MCP Server

Documentation Search MCP Server

by gemini2026
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

scan_project_dependencies

Scan project dependency files like pyproject.toml or requirements.txt for vulnerabilities and produce a detailed security report to help you fix potential risks.

Instructions

Scans project dependencies from files like pyproject.toml or requirements.txt for vulnerabilities.

Args:
    project_path: The path to the project directory (defaults to current directory).

Returns:
    A comprehensive security report of all project dependencies.

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

Input Schema

NameRequiredDescriptionDefault
project_pathNo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.1
  2. Removedv1.9.0
  3. First observed

TDQS

A3.8/5.0
Behavior2/5

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

No annotations provided, so description must carry burden of behavioral disclosure. It lacks information on side effects (e.g., read-only nature, network access, file modifications). Only states it scans and returns a report.

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?

Two sentences plus Args/Returns block that is clear and concise. Every sentence adds value with no redundancy.

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?

Adequately complete for a simple scanner: lists file types and return type. Could add more details about report contents, but sufficient given the tool's simplicity.

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

Parameters4/5

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

Schema has 0% description coverage for the single parameter, but the description explains the parameter (project_path) with purpose and default, adding value beyond the schema.

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 it scans project dependencies from files like pyproject.toml or requirements.txt for vulnerabilities, specifying both the resource and action, distinguishing it from similar tools.

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?

No explicit guidance on when to use this tool versus alternatives like snyk_scan_project or scan_library_vulnerabilities. The description only implies usage for local file scanning.

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

Deploy Server

Other Tools