postsleuth

Overview Schema Source Related Servers Discussions Admin

postfix_doctor

Read-only

One-call diagnosis of a Postfix server: queue summary, qshape of the deferred queue, log outcomes for the window, DNS authentication checks, and a list of findings with next steps.

Instructions

One-call diagnosis of a Postfix server: queue summary, qshape of the deferred queue, log outcomes for the window, DNS authentication checks, and a list of findings with next steps.

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

Input Schema

Name	Required	Description
`ips`	No	sending IPs
`since`	No	log window (default 24h)
`domain`	No	sending domain for DNS checks
`skip_dns`	No	do not run DNS checks

Output Schema

Name	Required	Description	Default
`dns`	No
`log`	No
`queue`	No
`shape`	No
`trend`	No
`config`	No
`findings`	Yes
`identity`	Yes
`problems`	Yes
`warnings`	Yes
`dns_error`	No
`log_error`	No
`queue_error`	No
`generated_at`	Yes
`provider_playbooks`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv0.2.1Oct 22, 2026

addedOutput schema / properties / findings / items / properties / playbook
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / findings / items / properties / references

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "title": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "title",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

addedOutput schema / properties / findings / items / properties / steps

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

addedOutput schema / properties / log / properties / stats / properties / bounce_causes / items / properties / playbook
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / log / properties / stats / properties / bounce_causes / items / properties / provider
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / log / properties / stats / properties / deferral_reasons / items / properties / playbook
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / log / properties / stats / properties / deferral_reasons / items / properties / provider
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / log / properties / stats / properties / smtpd_rejects / items / properties / playbook
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / log / properties / stats / properties / smtpd_rejects / items / properties / provider
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / provider_playbooks

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "bounces": {
+        "type": "integer"
+      },
+      "code_notes": {
+        "items": {
+          "type": "string"
+        },
+        "type": [
+          "null",
+          "array"
+        ]
+      },
+      "codes_seen": {
+        "items": {
+          "type": "string"
+        },
+        "type": [
+          "null",
+          "array"
+        ]
+      },
+      "deferred_attempts": {
+        "type": "integer"
+      },
+      "domains": {
+        "items": {
+          "type": "string"
+        },
+        "type": [
+          "null",
+          "array"
+        ]
+      },
+      "example": {
+        "type": "string"
+      },
+      "playbook": {
+        "additionalProperties": false,
+        "properties": {
+          "code_notes": {
+            "additionalProperties": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "codes": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "meaning": {
+            "type": "string"
+          },
+          "provider": {
+            "type": "string"
+          },
+          "references": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "title": {
+                  "type": "string"
+                },
+                "url": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "title",
+                "url"
+              ],
+              "type": "object"
+            },
+            "type": [
+              "null",
+              "array"
+            ]
+          },
+          "steps": {
+            "items": {
+              "type": "string"
+            },
+            "type": [
+              "null",
+              "array"
+            ]
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "provider",
+          "codes",
+          "title",
+          "meaning",
+          "steps",
+          "references"
+        ],
+        "type": "object"
+      },
+      "queued_recipients": {
+        "type": "integer"
+      },
+      "temporary": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "playbook",
+      "codes_seen",
+      "temporary",
+      "deferred_attempts",
+      "bounces",
+      "queued_recipients",
+      "domains",
+      "example"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

addedOutput schema / properties / queue / properties / reasons / items / properties / playbook
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / queue / properties / reasons / items / properties / provider
```
Added value: +{
+  "type": "string"
+}
```

First observedv0.1.0Oct 15, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations cover the safety profile (readOnly, non-open-world), so the description's job is to add operational context. It does disclose that output includes 'findings with next steps' and that DNS checks are part of the run, but it does not say the tool performs live DNS lookups, how expensive/slow an aggregated sweep is, what happens when ips/domain are omitted, or why idempotentHint is false (time-windowed results).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that names the tool's scope before enumerating components. Dense but every clause maps to real output; slightly long as an itemized list jammed into one sentence, but no filler.

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?

An output schema exists, so return values need not be explained. However, for a zero-required-parameter aggregator sitting among ten overlapping siblings, the definition is silent on what runs by default and how it relates to the individual tools, leaving the agent to guess selection policy.

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 description coverage is 100%, so parameters are already documented. The description only faintly reinforces them ('log outcomes for the window' hints at since, 'DNS authentication checks' hints at domain/skip_dns) without adding syntax, defaults, or interaction rules between ips and domain.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('One-call diagnosis of a Postfix server') and enumerates exactly which artifacts are produced: queue summary, qshape, log outcomes, DNS auth checks, findings. This is far more concrete than siblings like postfix_queue_summary or postfix_log_stats, though it never names those siblings to establish the bundling relationship explicitly.

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?

'One-call' implies this is a broad sweep versus the narrower sibling tools, but that inference is left to the agent. There is no explicit when-to-use/when-not, no statement that this supersedes calling postfix_queue_shape + mail_dns_check separately, and no guidance on cost/latency tradeoffs.

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

Deploy Server