Skip to main content
Glama
Sign In
qualys-mcp

qualys-mcp

by nelssec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

cache_status

View cache statistics and clear all caches in Qualys MCP to ensure up-to-date security data, resolving stale information issues.

Instructions

[Admin] Show cache stats or clear all caches.

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

Input Schema

NameRequiredDescriptionDefault
clearNoTrue to clear all caches, False to show stats only

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.9

TDQS

B3.3/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. It states the two modes (show stats/clear caches) but does not disclose side effects of clearing caches, such as performance impact, irreversibility, or potential disruption to other users.

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 a single, front-loaded sentence with no wasted words. The '[Admin]' tag gives immediate context, and all information is relevant and efficiently presented.

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

Completeness3/5

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

Given the simplicity of the tool (one boolean parameter and an output schema), the description is minimal but adequate for basic usage. However, the lack of any warning or context around the destructive 'clear' operation, combined with no annotations, leaves the description incomplete for safe usage.

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 coverage is 100%, and the parameter description already explains the 'clear' flag. The tool description essentially restates the parameter behavior without adding additional meaning, so it meets the baseline but doesn't exceed it.

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 displays cache statistics or clears all caches. The '[Admin]' prefix and verbs 'Show'/'clear' specify the action and resource, making it distinct from sibling security/risk tools.

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

Usage Guidelines2/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. The '[Admin]' prefix implies administrative context, but there is no mention of prerequisites, exclusions, or when clearing vs. showing is appropriate.

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