Skip to main content
Glama

devops-linux

nginx_config_audit

Audit nginx.conf directives for TLS 1.0/1.1 weak protocols, missing server_tokens off, missing HSTS/security headers, and brace balance.

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

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does add real value by disclosing the concrete audit dimensions rather than saying 'audit a config'. However, it never states that the operation is read-only and does not modify the target file, nor does it describe the shape of the findings (severity levels, pass/fail listing), which are the behaviors an agent most needs before invoking an unknown tool.

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 led by the verb, with every clause naming a distinct check rather than repeating the tool name. Nothing is wasted and the enumeration is the informative content, not filler.

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?

With no annotations and no output schema, the description is the only source of behavioral and input information, and it omits both the text-vs-filePath contract and any hint of what the audit returns. For a two-parameter tool where input selection is genuinely ambiguous, this leaves an agent unable to call it confidently.

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?

Schema description coverage is 0% and the description never mentions 'text' or 'filePath', so nothing is added beyond the bare property names. Critically, both parameters are optional with no stated precedence when both are supplied and no statement that one is effectively required — a decision the agent cannot resolve from the schema alone.

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 pairs a specific verb ('Audit') with a specific resource ('nginx.conf directives') and enumerates the exact checks performed: TLS 1.0/1.1, missing server_tokens off, missing HSTS/security headers, and brace balance. Naming nginx.conf explicitly also separates it from the sibling apache_config_audit without any inference needed.

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?

Usage is only implied by the enumerated checks: an agent can infer you run this on an nginx configuration, but the description never states when to prefer it over other audit tools or what prerequisites exist. There is no guidance at all on the practical decision an agent must make here — whether to pass inline config text or a file path.

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