Skip to main content
Glama
initMAX

Zabbix MCP Server

dhost_get

Read-only

Retrieve read-only discovered hosts found by Zabbix network discovery rules, including status and associated discovered services. Filter, search, or sort results to inspect discovery findings.

Instructions

Retrieve discovered hosts (read-only). Discovered hosts are hosts found by network discovery rules. Each discovered host may have one or more discovered services (dservice) representing the checks that succeeded.

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: dhostid, druleid, lastdown, lastup, status. Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the dhost 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: dhostid, druleid, status. Properties: dhostid, druleid, lastdown, lastup, status.
searchNoReturn results that match the given pattern (case-insensitive by default). Example: {"name": "web"} finds 'Web Server', 'my-web-app', etc.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
dhostidsNoReturn only discovered hosts with the given IDs.
druleidsNoReturn only discovered hosts found by the given network discovery rules.
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: dhostid, druleid (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 dhost.get parameters, merged into the request as-is. Parameters: dserviceids, limitSelects. Sub-object selects (value 'extend', 'count' or a list of property names): selectDRules, selectDServices. 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 '(read-only)' is largely a restatement; the genuinely additive content is the domain model (each dhost may have one or more dservices). It says nothing about pagination, result caps, permission requirements, or the raw_json/prompt-injection behavior that the schema documents.

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?

Two short sentences, front-loaded with the action and safety, then the domain relationship. No filler or redundancy.

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, rich 100%-covered parameters, and annotations carrying the safety profile, the description only needs to establish entity identity and it does so. It is slightly thin on how this tool relates to discoveryrule_get and dservice_get for an agent choosing among them, but nothing needed to call it correctly is missing.

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 all 14 parameters are documented in-schema, including filter keys, output, sort options, and the raw_json policy. The description adds no parameter meaning beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource ('Retrieve discovered hosts') and goes further by defining what a discovered host is ('hosts found by network discovery rules') and its relationship to dservices. It distinguishes the domain concept from the sibling dservice_get, though it never explicitly names a sibling as the alternative.

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?

Usage is only implied: an agent can infer this is the read tool for discovery-host entities, but there is no when-to-use statement, no prerequisite, and no explicit routing away from dservice_get or discoveryrule_get. Adequate but clearly gappy.

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