Skip to main content
Glama
initMAX

Zabbix MCP Server

hostprototype_get

Read-only

Retrieve and filter Zabbix host prototypes that define how LLD rules automatically create hosts, including groups, templates, and interfaces.

Instructions

Retrieve host prototypes. Host prototypes are used by LLD rules to automatically create new hosts for each discovered entity (e.g., VMware VMs discovered on a hypervisor). Each host prototype defines the groups, templates, and interfaces for the discovered hosts.

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: custom_interfaces (6.0+), discover, flags (7.4+), host, hostid, inventory_mode, name, status, templateid, uuid (6.0+). Text properties cannot be filtered; use 'search' for them.
outputNoProperties of the hostprototype 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: hostid, host, name, status. Properties: custom_interfaces (6.0+), discover, flags (7.4+), host, hostid, inventory_mode, name, status, templateid, uuid (6.0+).
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: host, name, uuid (6.0+).
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
hostidsNoReturn only host prototypes with the given 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.
sortfieldNoSort by one or more of: hostid, host, name, status, discover (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).
discoveryidsNoReturn only host prototypes belonging to the given LLD rules.
extra_paramsNoOther native hostprototype.get parameters, merged into the request as-is. Parameters: inherited. Sub-object selects (value 'extend', 'count' or a list of property names): selectDiscoveryData (7.4+), selectDiscoveryRule, selectDiscoveryRulePrototype (7.4+), selectGroupLinks, selectGroupPrototypes, selectInheritedTags (8.0+), selectInterfaces (6.0+), selectMacros, selectParentHost, selectTags (6.0+), selectTemplates. 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.7/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 the safety profile is covered without description text. The description adds no behavioral context beyond that (no pagination, auth, or scoping notes), so it neither helps nor contradicts.

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 front-loaded sentences: retrieval action first, then domain context. No filler, though the second and third sentences are explanatory rather than strictly necessary for invocation.

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 present, 14 fully documented params, and annotations covering the safety profile, the description only needs to anchor purpose and domain, which it does. The one gap is the absence of when-to-use guidance against siblings.

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% across all 14 parameters, so the schema already documents every argument in detail. The description adds no parameter 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Retrieve) and resource (host prototypes), then defines what a host prototype is (groups/templates/interfaces for hosts auto-created by LLD rules). This domain explanation distinguishes it clearly from siblings like discoveryrule_get or host_get.

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?

The description explains the domain concept but never says when to call this tool versus alternatives (e.g. discoveryrule_get, host_get, itemprototype_get). Usage is only implied by the concept explanation.

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