Skip to main content
Glama

devops-linux

apache_config_audit

Audit Apache httpd / .htaccess virtual hosts for Indexes directory listing leaks, weak ServerSignature, TraceEnable On, and RewriteRule flags.

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

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. 'Audit' implies a read-only analysis and the checks hint at behavior, but it never says whether the tool reads a file or inline text, what happens if both inputs are supplied, or what the findings output looks like (no output schema exists to cover this).

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?

A single front-loaded sentence that identifies the action, target, and check list with no filler. Density here is deliberate enumeration, not padding.

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?

For a tool with two undocumented input modes and no output schema or annotations, the description omits essential calling context: input precedence, expected config format, and result shape. The check list is useful but insufficient for correct invocation.

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

Parameters2/5

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

Two parameters (text, filePath) have 0% schema description coverage, and the description never mentions either one or how they relate. An agent cannot tell from the description whether filePath reads a file from disk, whether text is the config body, or whether they are mutually exclusive.

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?

States a specific verb ('Audit'), a specific resource ('Apache httpd / .htaccess virtual hosts'), and enumerates the exact checks performed (Indexes listings, ServerSignature, TraceEnable, RewriteRule flags). Naming Apache also implicitly separates it from the nginx_config_audit sibling.

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 use case (Apache config auditing) is implied by the resource named, but there is no explicit when-to-use guidance, no mention of the nginx_config_audit alternative, and no note on when this is inappropriate (e.g. non-Apache configs).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources