Skip to main content
Glama
Sign In
postsleuth

postsleuth

by Blackman99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

postfix_log_stats

Read-only

Aggregate the Postfix mail log over a time window: totals (received, sent, deferred attempts, bounced, expired, smtpd rejects), per-domain outcomes, domains still failing, grouped deferral reasons and bounce causes with category and hint…

Instructions

Aggregate the Postfix mail log over a time window: totals (received, sent, deferred attempts, bounced, expired, smtpd rejects), per-domain outcomes, domains still failing, grouped deferral reasons and bounce causes with category and hint, and DKIM selectors seen in signing logs.

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_log_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNomax entries per list (default 15)
sinceNotime window, e.g. 1h, 24h (default), 7d, or all
domainNoonly this recipient domain (leading dot = include subdomains)

Output Schema

NameRequiredDescriptionDefault
sinceYes
statsYes
sourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.2.1
    • addedOutput schema / properties / stats / properties / bounce_causes / items / properties / playbook
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / stats / properties / bounce_causes / items / properties / provider
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / stats / properties / deferral_reasons / items / properties / playbook
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / stats / properties / deferral_reasons / items / properties / provider
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / stats / properties / smtpd_rejects / items / properties / playbook
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / stats / properties / smtpd_rejects / items / properties / provider
      Added value: +{
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and idempotentHint=false, so the safety profile is covered. The description adds useful detail about what is summarized, including per-domain outcomes, failing domains, deferral/bounce groupings, and DKIM selectors. It does not add further behavioral context such as logging assumptions or performance limits.

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?

The description is a single dense sentence, front-loaded with the core action and scope. The enumerated outputs are useful for tool selection, though the list is long enough to be slightly burdensome.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 fully explained. Combined with annotations and fully described parameters, the description is sufficiently complete for an agent to invoke the tool correctly, though it lacks explicit sibling routing guidance.

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 all three parameters are already documented with their meanings and examples. The description reinforces the time-window concept but does not add syntax or edge-case semantics beyond the schema. A baseline 3 is appropriate.

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?

The description states a specific verb and resource: aggregate the Postfix mail log over a time window. It also enumerates the main metric families produced. It is clear what the tool does, though it does not explicitly differentiate itself from aggregate-oriented siblings such as postfix_log_trend or postfix_reason_categories.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies a summary/overview use case by saying it aggregates over a time window, but it does not say when to choose this over postfix_log_trace, postfix_log_trend, or postfix_reason_categories. No exclusions or alternative-selection guidance is provided.

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

Deploy Server

Other Tools