nginx-certbot-mcp

Overview Schema Source Related Servers Discussions Admin

reload_nginx

Idempotent

Test nginx configuration and reload the live service only when the test passes, preventing broken configs from being applied.

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
`hint`	No	Present on failure: how to recover, e.g. via rollback_site
`success`	Yes
`test_output`	Yes	Combined stdout/stderr of `nginx -t`

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.2Sep 19, 2026

addedOutput schema / properties / hint

Added value: +{
+  "description": "Present on failure: how to recover, e.g. via rollback_site",
+  "type": "string"
+}

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?

The description adds valuable behavioral context beyond the annotations: it guarantees 'never reloads a broken config' and explains that it runs a config test first. This supplements the idempotentHint and destructiveHint annotations. However, it doesn't mention what happens if the reload fails (e.g., error handling or return status), which could be relevant for an agent, though the output schema likely covers that.

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 sentences with no filler. The primary action and safety condition are front-loaded, followed by a direct usage instruction. Every word earns its place, making it highly efficient.

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, the description is fully sufficient. It explains what the tool does, when to use it, and provides a safety guarantee. There are no missing pieces that an agent needs to invoke it correctly.

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 parameters, and the input schema is empty. Per the rubric, 0 params implies a baseline score of 4. The description correctly omits parameter details since there are none, so nothing more is needed.

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 specific action ('Run nginx -t and reload the live service only if the config test passes') and resource ('live service'). It clearly distinguishes itself from sibling tools by specifying when to call it (after create_site, delete_site, or restore_site) and explicitly stating those tools do not reload automatically.

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 gives explicit usage context: 'Call this after create_site, delete_site, or restore_site to apply the change.' It also clarifies that those tools do not reload automatically, which tells the agent when this tool is necessary. This is clear, actionable guidance for when vs. when not to use it.

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