Skip to main content
Glama
initMAX

Zabbix MCP Server

item_threshold_search

Read-only

Find Zabbix items whose current lastvalue exceeds or falls below a numeric threshold. Filters client-side, skips non-numeric, and returns sorted results.

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

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

TableJSON 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, 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.itemid,name,key_,lastvalue
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
groupidsNoRestrict search to 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.
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. 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.
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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.41.0

TDQS

A4.4/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, but the description adds substantial behavior: it fetches all matching items via item.get and filters client-side, silently skips non-numeric lastvalues, and sorts results. It omits cost/perf implications of a full client-side scan, which keeps it from a 5.

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 first, mechanism second, worked examples third, return shape last. The return-format sentence is somewhat redundant given an output schema exists, but the overall structure is tight and each block is useful.

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, zero-required, read-only search tool with full schema coverage and an output schema, the description covers purpose, mechanism, filtering semantics, examples, and edge cases (non-numeric skipped). Nothing an agent needs to invoke it correctly 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 description coverage is 100%, so the schema already documents every parameter; baseline is 3. The description adds value by binding search keys to threshold params in worked examples and by clarifying the matched-vs-returned distinction that result_limit controls, which the schema does not spell out.

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?

The first sentence states a specific verb and resource with scope ('items whose current lastvalue is above or below a numeric threshold'). It also differentiates itself from the sibling item_get by noting it 'Replaces manual item_get + float(lastvalue) post-processing,' so an agent can route between them without opening schemas.

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

Usage Guidelines4/5

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

Three concrete 'typical uses' with real search/threshold pairings (SNAT pool >50%, discards >0, disk pused >=80) make the intended context very clear. There is no explicit when-NOT-to-use guidance or pointer to a sibling for cases like non-numeric or history-based lookups, so it stops short of a 5.

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