Skip to main content
Glama
initMAX

Zabbix MCP Server

httptest_get

Read-only

Retrieve web scenarios (HTTP tests) to verify web application availability, response times, and expected content. Filter results by host, template, or status.

Instructions

Retrieve web scenarios (HTTP tests). Web scenarios perform multi-step HTTP checks against web applications, verifying availability, response time, and expected content. Each scenario contains ordered steps and automatically creates web-monitoring items on the host.

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: agent, authentication, delay, headers, hostid, http_password, http_proxy, http_user, httptestid, name, nextcheck (removed in 6.4), retries, ssl_cert_file, ssl_key_file, ssl_key_password, status, templateid, uuid (6.0+), variables, verify_host, verify_peer. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the httptest 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: httptestid, hostid, name, status. Properties: agent, authentication, delay, headers, hostid, http_password, http_proxy, http_user, httptestid, name, nextcheck (removed in 6.4), retries, ssl_cert_file, ssl_key_file, ssl_key_password, status, templateid, uuid (6.0+), variables, verify_host, verify_peer.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: agent, delay, http_password, http_proxy, http_user, name, ssl_cert_file, ssl_key_file, ssl_key_password, uuid (6.0+).
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
hostidsNoReturn only web scenarios that belong to the given hosts.
groupidsNoReturn only web scenarios that belong to hosts in the given host groups.
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.
sortfieldNoSort by one or more of: httptestid, 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.
httptestidsNoReturn only web scenarios with the given IDs.
searchByAnyNoIf true, return results matching ANY search field (OR). Default is ALL fields (AND).
templateidsNoReturn only web scenarios that belong to the given templates.
extra_paramsNoOther native httptest.get parameters, merged into the request as-is. Parameters: evaltype (6.0+), expandName, expandStepName, inherited, inheritedTags (8.0+), monitored, tags (6.0+), templated. Sub-object selects (value 'extend', 'count' or a list of property names): selectHosts, selectInheritedTags (8.0+), selectSteps, selectTags (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.
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

B3.1/5.0
Behavior2/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 only domain background about what a web scenario is; it says nothing about this tool's own behavior (result size, filtering mechanics, the raw_json policy, or the auto-created monitoring items being an effect of scenario creation, not retrieval).

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?

Three compact sentences with the purpose front-loaded. The two background sentences on ordered steps and auto-created items are partly tangential to a read operation but do help the agent interpret results, and there is no filler or 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?

For a read-only list tool with a full output schema, 100% parameter coverage, and explicit annotations, the description supplies enough context to call it correctly. The main missing piece is routing guidance among the many sibling getters, which is a usage gap rather than a completeness one.

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 every one of the 16 parameters (filter, search, output, raw_json, extra_params, etc.) is already documented in the schema. The description adds no parameter-level meaning beyond that, making the baseline 3 appropriate.

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?

The description gives a clear verb + resource ('Retrieve web scenarios (HTTP tests)') and even glosses the otherwise obscure 'httptest' term, so an agent knows exactly what is returned. However, it never situates itself against the many sibling *_get tools (e.g. item_get, host_get) — it relies on the resource name alone for differentiation.

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

Usage Guidelines2/5

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

There is no when-to-use / when-not-to-use guidance and no named alternative for retrieving related monitoring objects. Usage is only implied by the word 'Retrieve'; nothing tells the agent when this tool is the right pick over a sibling or over extra_params-driven raw calls.

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