Skip to main content
Glama
initMAX

Zabbix MCP Server

script_get

Read-only

Retrieve Zabbix global scripts and filter them by host, host group, scope, type, or ID to find scripts available for manual execution or action operations.

Instructions

Retrieve global scripts configured in Zabbix. Scripts can be executed on hosts manually or as action operations. Types include custom script (0), IPMI (1), SSH (2), Telnet (3), webhook (5). Each script has a scope (action operation, manual host action, manual event action) and host group permissions. Use groupids/hostids to find scripts available for specific targets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return.
filterNoReturn only results whose properties exactly match the given values (a single value or a list of values per key). Example: {"status": 0} or {"status": [0, 1]}. Keys: authtype (6.0+), confirmation, description, execute_on, groupid, host_access, manualinput (7.0+), manualinput_default_value (7.0+), manualinput_prompt (7.0+), manualinput_validator (7.0+), manualinput_validator_type (7.0+), menu_path (6.0+), name, new_window (6.4+), parameters (6.0+), password (6.0+), port (6.0+), privatekey (6.0+), publickey (6.0+), scope (6.0+), scriptid, timeout (6.0+), type, url (6.4+), username (6.0+), usrgrpid. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the script 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: scriptid, name, type, scope. Properties: authtype (6.0+), command, confirmation, description, execute_on, groupid, host_access, manualinput (7.0+), manualinput_default_value (7.0+), manualinput_prompt (7.0+), manualinput_validator (7.0+), manualinput_validator_type (7.0+), menu_path (6.0+), name, new_window (6.4+), parameters (6.0+), password (6.0+), port (6.0+), privatekey (6.0+), publickey (6.0+), scope (6.0+), scriptid, timeout (6.0+), type, url (6.4+), username (6.0+), usrgrpid.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: command, confirmation, description, manualinput_default_value (7.0+), manualinput_prompt (7.0+), manualinput_validator (7.0+), menu_path (6.0+), name, password (6.0+), port (6.0+), privatekey (6.0+), publickey (6.0+), timeout (6.0+), url (6.4+), username (6.0+).
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
hostidsNoReturn only scripts available for the given host IDs.
groupidsNoReturn only scripts available for hosts in these host group IDs.
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.
scriptidsNoReturn only scripts with the given IDs.
sortfieldNoSort by one or more of: scriptid, name (comma-separated for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' (ascending) or 'DESC' (descending).
countOutputNoReturn the count of matching results instead of the actual data.
searchByAnyNoIf true, return results matching ANY search field (OR). Default is ALL fields (AND).
extra_paramsNoOther native script.get parameters, merged into the request as-is. Parameters: usrgrpids. Sub-object selects (value 'extend', 'count' or a list of property names): selectActions (6.0+), selectGroups (removed in 7.2), selectHostGroups (6.2+), selectHosts. 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.
searchWildcardsEnabledNoIf true, enable * and ? wildcards in search patterns.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.41.0

TDQS

A3.6/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 safety is covered. The description adds useful domain context (script types, scopes, host-group permissions) but no behavioral traits such as pagination, ordering defaults, or result-set size 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?

Four sentences, front-loaded with purpose then filtering scope; no filler. Slightly on the long side for a get tool, but every sentence carries domain information.

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

Completeness5/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; the description plus the exhaustively documented 15-parameter schema and annotations give an agent everything needed to call this correctly.

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% and each parameter is thoroughly documented, so the baseline is 3. The description restates the hostids/groupids filtering behavior already documented in the schema, adding no new semantics.

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 global scripts configured in Zabbix') and adds domain scope (types, action-operation vs manual execution). It does not name the close siblings script_getscriptsbyevents or script_getscriptsbyhosts, so an agent cannot fully distinguish it from them from the text alone.

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?

'Use groupids/hostids to find scripts available for specific targets' gives a concrete usage cue, but there is no explicit when-to-use/when-not guidance and no routing to the sibling *getscriptsby* tools that overlap heavily with this one. Adequate but incomplete.

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