nginx-certbot-mcp

Overview Schema Source Related Servers Discussions Admin

reload_nginx

Idempotent

Run nginx config test and reload the live service only if it passes, preventing broken configs from being applied. Call after create, delete, or restore site to apply changes.

Instructions

Run nginx -t and reload the live service only if the config test passes - never reloads a broken config. Call this after create_site, delete_site, or restore_site to apply the change; those tools do not reload automatically.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`success`	Yes
`test_output`	Yes	Combined stdout/stderr of `nginx -t`

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.1Sep 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "success": {
+      "type": "boolean"
+    },
+    "test_output": {
+      "description": "Combined stdout/stderr of `nginx -t`",
+      "type": "string"
+    }
+  },
+  "required": [
+    "success",
+    "test_output"
+  ],
+  "type": "object"
+}

First observedv0.1.0Sep 15, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already mark the tool as idempotent, non-destructive, and closed-world. The description adds useful behavioral context: it runs a config test first and only reloads if that passes this is not stated in the annotations. It does not describe response/exit behavior, but the output schema likely covers that, so this is a strong contribution.

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 two concise sentences. The first front-loads the core behavior and safety guard, and the second provides the exact invocation context. Every sentence earns its place with no filler or redundant restatement.

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?

For a zero-parameter tool with an output schema and annotations covering idempotency and destructiveness, the description is complete. It tells the agent what the tool does, when to call it, why it is needed, and what safety mechanism it uses. Nothing essential is missing.

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

Parameters4/5

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

The tool has zero parametersasi the schema confirms, and schema description coverage is 100%. Per the rubric, a zero-parameter tool gets a baseline of 4. The description does not need to explain parameters, and it does not attempt to invent any.

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 states a precise action: run `nginx -t` and reload the live service only if the config test passes. It clearly identifies the resource (nginx), the specific behavior (guarded reload), and the context that distinguishes it from sibling tools that modify site configs but do not reload.

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 explicitly says when to use the tool: after create_site, delete_site, or restore_site. It also clarifies that those tools do not reload automatically, which removes ambiguity about whether this step is needed. It also implies a key constraint: never reloads a broken config.

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