Skip to main content
Glama
initMAX

Zabbix MCP Server

settings_get

Read-only

Retrieve global Zabbix server settings, including theme, URL, timeouts, severity names and colors, login defaults, and other global configuration. Returns the full singleton settings object.

Instructions

Get global Zabbix server settings. Returns the singleton settings object containing: default theme, server name, frontend URL, alert notification timeout, severity name overrides, severity colors, custom color settings, login and session parameters, and various other global defaults. No filtering options -- returns the full object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
outputNoProperties of the settings 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: alert_usrgrpid, apm_global_db (8.0+), auditlog_enabled (6.0+), auditlog_mode (7.0+), blink_period, connect_timeout, custom_color, default_inventory_mode, default_lang, default_theme, default_timezone, device_link_timeout (8.0+), discovery_groupid, geomaps_attribution (6.0+), geomaps_max_zoom (6.0+), geomaps_tile_provider (6.0+), geomaps_tile_url (6.0+), ha_failover_delay (6.0+), history_period, iframe_sandboxing_enabled, iframe_sandboxing_exceptions, item_test_timeout, login_attempts, login_block, max_in_table, max_overview_table_size, max_period, media_type_test_timeout, ok_ack_color, ok_ack_style, ok_period, ok_unack_color, ok_unack_style, period_default, problem_ack_color, problem_ack_style, problem_unack_color, problem_unack_style, proxy_secrets_provider (7.4+), report_test_timeout (5.4+), script_timeout, search_limit, server_check_interval, serverid (8.0+), severity_color_0, severity_color_1, severity_color_2, severity_color_3, severity_color_4, severity_color_5, severity_name_0, severity_name_1, severity_name_2, severity_name_3, severity_name_4, severity_name_5, show_technical_errors, snmptrap_logging, socket_timeout, timeout_browser (7.0+), timeout_db_monitor (7.0+), timeout_external_check (7.0+), timeout_http_agent (7.0+), timeout_script (7.0+), timeout_simple_check (7.0+), timeout_snmp_agent (7.0+), timeout_ssh_agent (7.0+), timeout_telemetry_query (8.0+), timeout_telnet_agent (7.0+), timeout_zabbix_agent (7.0+), uri_valid_schemes, url (5.4+), validate_uri_schemes, vault_provider (6.2+), work_period, x_frame_options.
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 settings.get parameters, merged into the request as-is. settings.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
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that it returns the full object with no filtering, which is useful scope context, but says nothing about output size, auth requirements, or whether the response is wrapped (the raw_json/prompt-injection wrapping behavior lives only in the schema).

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 sentences, front-loaded with the verb and resource, then contents, then scope constraint. No filler and no repetition.

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 the read-only/singleton semantics are fully conveyed for an agent to call this correctly. Slightly incomplete only in that it never hints at auth scoping or when a caller might prefer a narrower sibling.

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 the schema fully documents output/server/raw_json/extra_params; baseline is 3. The description's field enumeration partly overlaps the 'output' property's own property list and adds no format or default syntax beyond it.

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?

States a specific verb and resource ('Get global Zabbix server settings'), and explicitly identifies the singleton nature ('the singleton settings object'), which separates it from the many resource-*_get siblings. The enumerated contents confirm exactly what domain it operates on.

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?

The 'No filtering options -- returns the full object' line implies this is the unfiltered global-settings read, but there is no explicit when-to-use/when-not guidance and no named alternative (e.g. serverinfo_get or housekeeping_get) for overlapping concerns. Usage is inferable but not spelled out.

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