mcp-nagios-crunchtools

Nagios Notification History Tool

nagios_notification_history_tool

Read-only

Retrieve recent Nagios notification history for all hosts or a specific host within a chosen time window, so you can review who was alerted and when.

Instructions

Retrieve recent notification history from Nagios.

Input Schema

Name	Required	Description	Default
`hours`	No	How many hours of history to retrieve, 1 to 744. Default 24.
`host_name`	No	Filter to a specific host. Omit for all hosts.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.5.0Oct 17, 2026

changedInput schema / properties / host_name / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 255,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / hours / description

Previous value: -"How many hours of history to retrieve. Default 24."New value: +"How many hours of history to retrieve, 1 to 744. Default 24."

addedInput schema / properties / hours / maximum
```
Added value: +744
```
addedInput schema / properties / hours / minimum
```
Added value: +1
```

First observedv0.1.0Aug 23, 2026

TDQS

B3.1/5.0

Behavior2/5

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

The readOnlyHint annotation already establishes this is a safe read operation, so the description's main remaining job is to add context beyond that. It adds only 'recent' and 'notification history,' with no mention of source, scope, pagination, or freshness beyond what the schema/annotations imply.

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 with no redundant or filler content. It is appropriately sized for a simple two-parameter retrieval tool.

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 and annotations cover the safety profile, so return values and safety need not be explained. However, the description omits any routing guidance relative to the overlapping alert-history sibling, leaving an agent to infer usage.

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 both the hours range/default and the host_name filter are fully documented in the schema. The description adds no parameter detail beyond that, which is the expected baseline when the schema does the heavy lifting.

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 and resource ('Retrieve recent notification history from Nagios'), so the agent knows it fetches notification events. It does not, however, distinguish this from the sibling nagios_alert_history_tool or clarify the notification-vs-alert distinction, leaving potential sibling confusion.

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?

No guidance on when to use this tool versus nagios_alert_history_tool or nagios_current_problems_tool, and no exclusions or prerequisites. 'Recent' is the only contextual hint, and it is already implicit in the hours parameter.

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

Deploy Server