Skip to main content
Glama
shyshlakov

pci-dss-mcp

generate_compliance_report

Generate a PCI DSS v4.0.1 compliance report for Go payment services, providing requirement-level pass/fail lists and severity-filtered findings for CI gates and audit artifacts.

Instructions

Raw PCI DSS v4.0.1 compliance report without AI triage — intended for CI gates, audit artifacts, and requirement-level pass/fail lists. For interactive "scan this project" prompts call triage_findings instead. Default unfiltered call returns a compact summary (metadata, totals, requirement_statuses, top 20 findings per severity, cursor for follow-up). Supply min_severity / rule_filter / limit to get a paged flat list (60 per page with cursor), or cursor= to resume a prior session (10-minute TTL). min_severity / rule_filter drop the response to shape "flat" but still carry summary.by_severity + summary.by_rule for full-scan context. Taint analysis is ON by default; set include_taint=false for fast dev iteration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the Go project to scan for PCI DSS compliance. If empty, uses current directory (.)
dep_scan_modeNoDependency scanner mode: only 'auto' (default) is supported after v0.6.3. Empty value is treated as 'auto'.
include_testsNoInclude _test.go files in scan results. Default false excludes test files per industry SAST consensus
include_taintNoEnable flow-based severity adjustment via go/packages type analysis. When true, panscanner downgrades PAN-KEYWORD and suppresses PAN-TYPE findings for transit-only CHD fields (request/response DTOs, API client models) per and the PCI SSC FAQ on non-persistent memory. Adds 5-30 seconds to scan time. Default true (production-grade precision). Set false for fast dev iteration. Requires 'go' binary on PATH; falls back to AST-only scanning on failure.
min_severityNoFilter findings by minimum severity. One of CRITICAL / HIGH / MEDIUM / LOW / INFO (case-insensitive). Default: no severity filter. Useful for AI clients that only need HIGH-or-above results.
rule_filterNoFilter findings by rule ID. Comma-separated list for exact match (e.g. PAN-KEYWORD,PAN-TYPE) OR a single regex in leading/trailing slashes (e.g. /PAN-.*/). Default: no rule filter.
limitNoMaximum number of findings to return per call. Default 0 (summary-first response with next_cursor). To fetch more findings than fit in one response, follow next_cursor; do NOT raise this value to fetch all at once (server caps at the per-tool page size and rejects with LIMIT_EXCEEDS_PAGE_SIZE).
cursorNoOpaque cursor token from a prior response. When set, resumes pagination from the stored session cache (10-minute TTL). Leave empty for a fresh scan.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully discloses behavior: default output structure, effect of filters on response shape, cursor TTL (10 minutes), taint analysis default behavior, dependency on 'go' binary, and fallback to AST-only. It details taint analysis logic (downgrading PAN-KEYWORD, suppressing PAN-TYPE) and suggests when to disable it.

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 and front-loaded with purpose and usage guidance. Every sentence adds necessary information without redundancy. Despite length, it remains concise and informative.

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 tool's complexity (8 parameters, no annotations, output schema exists), the description is highly complete. It covers response shape, pagination, taint analysis details, fallback behavior, and when to use sibling tool. The output schema handles return value details, so the description focuses on high-level behavior and usage.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant value: explains default path behavior, provides rationale for include_taint, warns against raising limit, describes cursor TTL, and gives usage examples for min_severity and rule_filter syntax. This enriches the schema descriptions.

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 the tool generates a 'Raw PCI DSS v4.0.1 compliance report without AI triage' for CI gates and audit artifacts, and distinguishes it from triage_findings for interactive use. The verb 'generate' and resource 'compliance report' are explicit.

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: 'For interactive prompts call triage_findings instead.' It explains when to use different parameters (min_severity, rule_filter, limit, cursor) and the default summary-first response vs. paginated flat list. It also warns against raising limit above server cap and describes cursor TTL.

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/shyshlakov/pci-dss-mcp'

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