Skip to main content
Glama
initMAX

Zabbix MCP Server

by initMAX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

housekeeping_get

Read-only

Retrieve Zabbix cleanup settings to review automatic data retention periods for history, trends, events, alerts, sessions, and audit logs. Use it to inspect cleanup configuration.

Instructions

Get housekeeping settings. Returns the global configuration that controls automatic cleanup of old data: history storage period, trend storage period, event and alert retention, session cleanup interval, and audit log retention. This is a singleton object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
outputNoProperties of the housekeeping object to return. Pass 'extend' for all, 'count' for the number of matches only, or a comma-separated list of property names. Default when omitted: 'extend'. Properties: compress_older, compression_status, db_extension, hk_audit, hk_audit_mode, hk_events_autoreg, hk_events_discovery, hk_events_internal, hk_events_mode, hk_events_service (6.0+), hk_events_trigger, hk_history, hk_history_global, hk_history_mode, hk_services, hk_services_mode, hk_sessions, hk_sessions_mode, hk_trends, hk_trends_global, hk_trends_mode.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
raw_jsonNoStrips the security disclaimer preamble from the response so it is pure JSON. Default: false. Requires the bearer token to have 'allow_raw_json' explicitly enabled by an operator in the admin portal - tokens without that policy receive a PolicyError instead. WARNING: setting true bypasses the prompt-injection mitigation marker that wraps untrusted Zabbix data (host names, item descriptions, problem text). LLM clients (Claude, GPT, Cursor, ...) should leave this false; only programmatic non-LLM consumers (Python scripts, n8n workflows that json.loads the result) should set true.
extra_paramsNoOther native housekeeping.get parameters, merged into the request as-is. housekeeping.get has no parameters beyond the typed ones. Any other key is refused here, because Zabbix would silently ignore it. For a parameter you are sure exists on your release but is not listed, use zabbix_raw_api_call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.41.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered structurally. The description adds a genuinely useful behavioral fact — that this is a singleton object with no per-entity targeting — which tells the agent there is no ID or filtering dimension to supply.

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?

Three tight sentences, front-loaded with the action, then the returned fields, then the singleton scope note. No redundant or filler text.

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?

With an output schema present, return values need not be described, and annotations cover the safety profile. The description supplies the singleton nature and a field-level summary, leaving only the routine when-to-use routing as a minor gap.

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 four parameters (output, server, raw_json, extra_params) are fully documented in the schema, including the raw_json security warning. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 ('Get housekeeping settings') and then enumerates exactly what configuration it returns (history/trend storage periods, event and alert retention, session cleanup interval, audit log retention). An agent knows precisely what this tool fetches, though it does not explicitly distinguish itself from neighbors like settings_get or serverinfo_get.

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?

Usage is only implied by the content of the returned data — an agent would use it to inspect cleanup/retention configuration. There is no explicit when-to-use statement, no exclusions, and no pointer to siblings when a different settings surface is actually wanted.

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