Skip to main content
Glama
Sign In
qualys-mcp

qualys-mcp

by nelssec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

reports

List templates, generate reports in PDF/HTML/CSV, check status, download, and delete Qualys security reports. Automate reporting workflows.

Instructions

[Reporting] Unified report operations — list, templates, generate, status, download, delete.

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": {
      "action": "<action>"
    },
    "name": "reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes"list" | "templates" | "generate" | "status" | "download" | "delete"
report_idNoreport ID (for status/download/delete)
template_idNotemplate ID (for generate)
report_titleNocustom title for generated report
output_formatNo"pdf" | "html" | "mht" | "xml" | "csv" | "docx" (default pdf)pdf
template_nameNofilter templates by name substring
asset_group_idsNocomma-separated asset group IDs (for generate)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.9

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only lists actions without explaining side effects, permissions, rate limits, or what happens after execution. This is a significant gap for a multi-action tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief and front-loaded with a '[Reporting]' tag, but it's terse to the point of omitting necessary context for a tool with 7 parameters and 6 actions. It's concise but under-specified.

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

Completeness2/5

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

Given the tool's complexity (multiple actions, 7 params), the description fails to provide enough contextual information. The schema covers parameter details well, but the description doesn't explain the purpose of each action, usage sequence, or operational dependencies. Output schema may cover return values, but operational context is missing.

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 description coverage is 100%, so the baseline is 3. The description adds no additional parameter meaning beyond repeating the action list, which is already fully described in the schema's action parameter.

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 identifies the tool as handling report operations and enumerates the supported actions (list, templates, generate, status, download, delete). This clearly distinguishes it from the security-focused sibling tools. However, it doesn't elaborate on what each action does, so it's clear but not fully detailed.

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 description implies usage for any report-related task by listing the available actions, but it doesn't explicitly state when to prefer this tool over alternatives or when to use each action. No exclusions or alternative references are provided.

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