Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

item_threshold_search

Read-only

Finds Zabbix items whose current values exceed or fall below numeric thresholds, enabling quick checks of utilization, capacity, and counters without manual post-processing.

Instructions

Find items whose current lastvalue is above or below a numeric threshold.

Fetches all items matching the query via item.get, filters client-side by lastvalue, and returns sorted results. Non-numeric lastvalues are skipped. Replaces manual item_get + float(lastvalue) post-processing.

Typical uses:

  • SNAT pool utilization above 50%: search={"key_": ".usage"}, lastvalue_ge=50

  • Interface discard counter above 0: search={"key_": "discards"}, lastvalue_gt=0

  • Disk usage near capacity: search={"key_": "pused"}, lastvalue_ge=80

Which key carries a metric depends on the templates in use (memory may be 'vm.memory.utilization', 'vm.memory.size[pused]' or 'vm.memory.size[pavailable]'; a disk has one 'vfs.fs.size[,pused]' item per filesystem). A key fragment must come from the items that exist: when it is not known, look first with item_get (search on name or key_, output itemid, name, key_, units, value_type) and use the key_ it returns. The threshold is compared with lastvalue as stored, so check 'units' (a percentage versus bytes).

Returns {"scanned": N, "matched": M, "returned": R, "items": [...]} sorted by lastvalue. matched = total passing threshold; returned = items included (may be less if result_limit set).

Input Schema

NameRequiredDescriptionDefault
filterNoExact-match filter, e.g. {"type": 0} for Zabbix agent items. Return 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: allow_traps, authtype, delay, enabled_lifetime (7.0+), enabled_lifetime_type (7.0+), evaltype, flags, follow_redirects, formula, granularity (8.0+), history, hostid, http_proxy, interfaceid, inventory_link, ipmi_sensor, itemid, jmx_endpoint, key_, lifetime, lifetime_type (7.0+), logtimefmt, lookback_limit (8.0+), master_itemid, name, name_resolved (7.0+), output_format, password, post_type, privatekey, publickey, request_method, retrieve_mode, snmp_oid, ssl_cert_file, ssl_key_file, ssl_key_password, state, status, status_codes, templateid, time_shift (8.0+), timeout, trapper_hosts, trends, type, units, url, username, uuid (6.0+), value_type, valuemapid, verify_host, verify_peer. Text properties cannot be filtered; use 'search' for them.
outputNoItem properties to return: a list of names, or 'extend'. Default: itemid, name, key_, lastvalue; lastvalue is always included for the threshold. Properties: allow_traps, authtype, delay, description, enabled_lifetime (7.0+), enabled_lifetime_type (7.0+), error, evaltype, flags, follow_redirects, formula, granularity (8.0+), headers, history, hostid, http_proxy, interfaceid, inventory_link, ipmi_sensor, itemid, jmx_endpoint, key_, lastclock, lastns, lastvalue, lifetime, lifetime_type (7.0+), logtimefmt, lookback_limit (8.0+), master_itemid, name, name_resolved (7.0+), output_format, parameters (6.0+), params, password, post_type, posts, prevvalue, privatekey, publickey, query (8.0+), query_fields, request_method, retrieve_mode, snmp_oid, ssl_cert_file, ssl_key_file, ssl_key_password, state, status, status_codes, templateid, time_shift (8.0+), timeout, trapper_hosts, trends, type, units, url, username, uuid (6.0+), value_type, valuemapid, verify_host, verify_peer.
searchNoSubstring search, e.g. {"key_": "discards"} or {"key_": ".usage"} ('discards' matches 'net.if.in.discards[eth0]'). Return results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: delay, description, error, formula, granularity (8.0+), history, http_proxy, ipmi_sensor, jmx_endpoint, key_, lifetime, logtimefmt, lookback_limit (8.0+), name, name_resolved (7.0+), params, password, posts, privatekey, publickey, snmp_oid, ssl_cert_file, ssl_key_file, ssl_key_password, status_codes, time_shift (8.0+), timeout, trapper_hosts, trends, units, url, username, uuid (6.0+).
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
hostidsNoRestrict search to these host IDs (from host_get)
groupidsNoRestrict search to these host group IDs (from hostgroup_get)
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.
sort_descNoSort matched items by lastvalue descending — highest values first (default: true)
extra_paramsNoAdditional item.get parameters, e.g. {"selectHosts": ["host"]} for the host name or {"searchWildcardsEnabled": true} for wildcards. Other native item.get parameters, merged into the request as-is. Parameters: evaltype (6.0+), graphids, group, host, inherited, inheritedTags (8.0+), interfaceids, itemids, limitSelects, monitored, proxyids, tags (6.0+), templated, templateids, triggerids, webitems, with_triggers. Switches (true turns one on, false is the same as leaving it out): webitems. Sub-object selects (value 'extend', 'count' or a list of property names): selectDiscoveryData (7.4+), selectDiscoveryRule, selectGraphs, selectHosts, selectInheritedTags (8.0+), selectInterfaces, selectItemDiscovery (deprecated in 7.4, use selectDiscoveryData), selectPreprocessing, selectTags (6.0+), selectTriggers, selectValueMap (6.0+). 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.
lastvalue_geNoKeep only items where lastvalue >= this value (e.g. 50.0 to find SNAT pools above 50% utilization)
lastvalue_gtNoKeep only items where lastvalue > this value (strict greater-than)
lastvalue_leNoKeep only items where lastvalue <= this value
lastvalue_ltNoKeep only items where lastvalue < this value (strict less-than)
result_limitNoMax number of matched items to return after threshold filtering

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.42.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / extra_params / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "editable",
      +        "excludeSearch",
      +        "limit",
      +        "searchByAny",
      +        "searchWildcardsEnabled",
      +        "sortfield",
      +        "sortorder",
      +        "startSearch",
      +        "evaltype",
      +        "graphids",
      +        "group",
      +        "host",
      +        "inherited",
      +        "inheritedTags",
      +        "interfaceids",
      +        "itemids",
      +        "limitSelects",
      +        "monitored",
      +        "proxyids",
      +        "tags",
      +        "templated",
      +        "templateids",
      +        "triggerids",
      +        "webitems",
      +        "with_triggers",
      +        "application",
      +        "applicationids",
      +        "selectDiscoveryData",
      +        "selectDiscoveryRule",
      +        "selectGraphs",
      +        "selectHosts",
      +        "selectInheritedTags",
      +        "selectInterfaces",
      +        "selectItemDiscovery",
      +        "selectPreprocessing",
      +        "selectTags",
      +        "selectTriggers",
      +        "selectValueMap",
      +        "selectApplications"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / extra_params / description
      Previous value: -"Additional item.get parameters, e.g. {\"selectHosts\": [\"host\"]} for the host name or {\"searchWildcardsEnabled\": true} for wildcards. Other native item.get parameters, merged into the request as-is. Parameters: evaltype (6.0+), graphids, group, host, inherited, inheritedTags (8.0+), interfaceids, itemids, limitSelects, monitored, proxyids, tags (6.0+), templated, templateids, triggerids, webitems, with_triggers. Sub-object selects (value 'extend', 'count' or a list of property names): selectDiscoveryData (7.4+), selectDiscoveryRule, selectGraphs, selectHosts, selectInheritedTags (8.0+), selectInterfaces, selectItemDiscovery, selectPreprocessing, selectTags (6.0+), selectTriggers, selectValueMap (6.0+). 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."New value: +"Additional item.get parameters, e.g. {\"selectHosts\": [\"host\"]} for the host name or {\"searchWildcardsEnabled\": true} for wildcards. Other native item.get parameters, merged into the request as-is. Parameters: evaltype (6.0+), graphids, group, host, inherited, inheritedTags (8.0+), interfaceids, itemids, limitSelects, monitored, proxyids, tags (6.0+), templated, templateids, triggerids, webitems, with_triggers. Switches (true turns one on, false is the same as leaving it out): webitems. Sub-object selects (value 'extend', 'count' or a list of property names): selectDiscoveryData (7.4+), selectDiscoveryRule, selectGraphs, selectHosts, selectInheritedTags (8.0+), selectInterfaces, selectItemDiscovery (deprecated in 7.4, use selectDiscoveryData), selectPreprocessing, selectTags (6.0+), selectTriggers, selectValueMap (6.0+). 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."
    • changedInput schema / properties / filter / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "allow_traps",
      +        "authtype",
      +        "delay",
      +        "enabled_lifetime",
      +        "enabled_lifetime_type",
      +        "evaltype",
      +        "flags",
      +        "follow_redirects",
      +        "formula",
      +        "granularity",
      +        "history",
      +        "hostid",
      +        "http_proxy",
      +        "interfaceid",
      +        "inventory_link",
      +        "ipmi_sensor",
      +        "itemid",
      +        "jmx_endpoint",
      +        "key_",
      +        "lifetime",
      +        "lifetime_type",
      +        "logtimefmt",
      +        "lookback_limit",
      +        "master_itemid",
      +        "name",
      +        "name_resolved",
      +        "output_format",
      +        "password",
      +        "post_type",
      +        "privatekey",
      +        "publickey",
      +        "request_method",
      +        "retrieve_mode",
      +        "snmp_oid",
      +        "ssl_cert_file",
      +        "ssl_key_file",
      +        "ssl_key_password",
      +        "state",
      +        "status",
      +        "status_codes",
      +        "templateid",
      +        "time_shift",
      +        "timeout",
      +        "trapper_hosts",
      +        "trends",
      +        "type",
      +        "units",
      +        "url",
      +        "username",
      +        "uuid",
      +        "value_type",
      +        "valuemapid",
      +        "verify_host",
      +        "verify_peer"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / groupids / description
      Previous value: -"Restrict search to these host group IDs"New value: +"Restrict search to these host group IDs (from hostgroup_get)"
    • changedInput schema / properties / hostids / description
      Previous value: -"Restrict search to these host IDs"New value: +"Restrict search to these host IDs (from host_get)"
    • changedInput schema / properties / output / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "extend"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "allow_traps",
      +        "authtype",
      +        "delay",
      +        "description",
      +        "enabled_lifetime",
      +        "enabled_lifetime_type",
      +        "error",
      +        "evaltype",
      +        "flags",
      +        "follow_redirects",
      +        "formula",
      +        "granularity",
      +        "headers",
      +        "history",
      +        "hostid",
      +        "http_proxy",
      +        "interfaceid",
      +        "inventory_link",
      +        "ipmi_sensor",
      +        "itemid",
      +        "jmx_endpoint",
      +        "key_",
      +        "lastclock",
      +        "lastns",
      +        "lastvalue",
      +        "lifetime",
      +        "lifetime_type",
      +        "logtimefmt",
      +        "lookback_limit",
      +        "master_itemid",
      +        "name",
      +        "name_resolved",
      +        "output_format",
      +        "parameters",
      +        "params",
      +        "password",
      +        "post_type",
      +        "posts",
      +        "prevvalue",
      +        "privatekey",
      +        "publickey",
      +        "query",
      +        "query_fields",
      +        "request_method",
      +        "retrieve_mode",
      +        "snmp_oid",
      +        "ssl_cert_file",
      +        "ssl_key_file",
      +        "ssl_key_password",
      +        "state",
      +        "status",
      +        "status_codes",
      +        "templateid",
      +        "time_shift",
      +        "timeout",
      +        "trapper_hosts",
      +        "trends",
      +        "type",
      +        "units",
      +        "url",
      +        "username",
      +        "uuid",
      +        "value_type",
      +        "valuemapid",
      +        "verify_host",
      +        "verify_peer"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / default
      Previous value: -"itemid,name,key_,lastvalue"New value: +null
    • changedInput schema / properties / output / description
      Previous value: -"Item properties to return, comma-separated, or 'extend'. Default 'itemid,name,key_,lastvalue'; lastvalue is always included for the threshold. Properties: allow_traps, authtype, delay, description, enabled_lifetime (7.0+), enabled_lifetime_type (7.0+), error, evaltype, flags, follow_redirects, formula, granularity (8.0+), headers, history, hostid, http_proxy, interfaceid, inventory_link, ipmi_sensor, itemid, jmx_endpoint, key_, lastclock, lastns, lastvalue, lifetime, lifetime_type (7.0+), logtimefmt, lookback_limit (8.0+), master_itemid, name, name_resolved (7.0+), output_format, parameters (6.0+), params, password, post_type, posts, prevvalue, privatekey, publickey, query (8.0+), query_fields, request_method, retrieve_mode, snmp_oid, ssl_cert_file, ssl_key_file, ssl_key_password, state, status, status_codes, templateid, time_shift (8.0+), timeout, trapper_hosts, trends, type, units, url, username, uuid (6.0+), value_type, valuemapid, verify_host, verify_peer."New value: +"Item properties to return: a list of names, or 'extend'. Default: itemid, name, key_, lastvalue; lastvalue is always included for the threshold. Properties: allow_traps, authtype, delay, description, enabled_lifetime (7.0+), enabled_lifetime_type (7.0+), error, evaltype, flags, follow_redirects, formula, granularity (8.0+), headers, history, hostid, http_proxy, interfaceid, inventory_link, ipmi_sensor, itemid, jmx_endpoint, key_, lastclock, lastns, lastvalue, lifetime, lifetime_type (7.0+), logtimefmt, lookback_limit (8.0+), master_itemid, name, name_resolved (7.0+), output_format, parameters (6.0+), params, password, post_type, posts, prevvalue, privatekey, publickey, query (8.0+), query_fields, request_method, retrieve_mode, snmp_oid, ssl_cert_file, ssl_key_file, ssl_key_password, state, status, status_codes, templateid, time_shift (8.0+), timeout, trapper_hosts, trends, type, units, url, username, uuid (6.0+), value_type, valuemapid, verify_host, verify_peer."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "delay",
      +        "description",
      +        "error",
      +        "formula",
      +        "granularity",
      +        "history",
      +        "http_proxy",
      +        "ipmi_sensor",
      +        "jmx_endpoint",
      +        "key_",
      +        "lifetime",
      +        "logtimefmt",
      +        "lookback_limit",
      +        "name",
      +        "name_resolved",
      +        "params",
      +        "password",
      +        "posts",
      +        "privatekey",
      +        "publickey",
      +        "snmp_oid",
      +        "ssl_cert_file",
      +        "ssl_key_file",
      +        "ssl_key_password",
      +        "status_codes",
      +        "time_shift",
      +        "timeout",
      +        "trapper_hosts",
      +        "trends",
      +        "units",
      +        "url",
      +        "username",
      +        "uuid"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "_item_threshold_searchOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv1.41.0

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses that all matching items are fetched via item.get and filtered client-side (a performance-relevant trait), that non-numeric lastvalues are silently skipped, and that comparison happens against the stored value. It also documents the return envelope and the matched-vs-returned distinction. Only missing context is any practical guidance on how large 'scanned' can get.

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?

Well front-loaded: purpose, mechanism, caveats, examples, return shape - in that order. It is somewhat long and the parenthetical about memory key variants plus the repeated reminder to use item_get add bulk, but every block is informative rather than filler.

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?

For a 14-parameter tool with no output schema, the description supplies the return envelope, default returned fields, sort order, and the numeric-coercion caveat. Nothing an agent needs to call it correctly or interpret the result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by showing concrete search/threshold pairings and by explaining that result_limit can make 'returned' smaller than 'matched'. It also flags that filter keys are exact-match only and text should go to 'search' - though that is partly restated from the schema.

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?

Opens with a specific verb and resource - 'Find items whose current lastvalue is above or below a numeric threshold' - which precisely names the operation and its distinguishing criterion. An agent can immediately tell this apart from item_get (raw listing) and history_get (time series).

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

Usage Guidelines5/5

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

Gives three concrete usage scenarios with parameter examples (SNAT pool utilization, discard counters, disk usage), explicitly names item_get as the prerequisite when the key fragment is unknown, and warns to check 'units' before setting a threshold. It states both when to use it and how to prepare for it.

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