Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

hostprototype_get

Read-only

Retrieve host prototypes used by low-level discovery rules to automatically create hosts for discovered entities, including their assigned 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

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 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 (a list 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: groupCount, inherited. Switches (true turns one on, false is the same as leaving it out): groupCount. groupCount goes with output='count': the count is then split by the ID filters the method groups by (hostids, groupids ...), one row per ID with 'rowscount'; a single row without such a filter. 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.

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",
      +        "preservekeys",
      +        "startSearch",
      +        "groupCount",
      +        "inherited",
      +        "selectDiscoveryData",
      +        "selectDiscoveryRule",
      +        "selectDiscoveryRulePrototype",
      +        "selectGroupLinks",
      +        "selectGroupPrototypes",
      +        "selectInheritedTags",
      +        "selectInterfaces",
      +        "selectMacros",
      +        "selectParentHost",
      +        "selectTags",
      +        "selectTemplates"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / extra_params / description
      Previous value: -"Other 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."New value: +"Other native hostprototype.get parameters, merged into the request as-is. Parameters: groupCount, inherited. Switches (true turns one on, false is the same as leaving it out): groupCount. groupCount goes with output='count': the count is then split by the ID filters the method groups by (hostids, groupids ...), one row per ID with 'rowscount'; a single row without such a filter. 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."
    • changedInput schema / properties / filter / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "custom_interfaces",
      +        "discover",
      +        "flags",
      +        "host",
      +        "hostid",
      +        "inventory_mode",
      +        "name",
      +        "status",
      +        "templateid",
      +        "uuid"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "extend",
      +      "count"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "custom_interfaces",
      +        "discover",
      +        "flags",
      +        "host",
      +        "hostid",
      +        "inventory_mode",
      +        "name",
      +        "status",
      +        "templateid",
      +        "uuid"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / description
      Previous value: -"Properties 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+)."New value: +"Properties of the hostprototype object to return. Pass 'extend' for all, 'count' for the number of matches only, or a 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+)."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "host",
      +        "name",
      +        "uuid"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "hostid",
      +      "host",
      +      "name",
      +      "status",
      +      "discover"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "hostid",
      +        "host",
      +        "name",
      +        "status",
      +        "discover"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: hostid, host, name, status, discover (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: hostid, host, name, status, discover (a list for several; pair with 'sortorder'). No other property is sortable."
    • changedInput schema / properties / sortorder / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "ASC",
      +      "DESC"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "ASC",
      +        "DESC"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "hostprototype_getOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv1.41.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds domain context useful for interpreting returned entities but says nothing about pagination, default output fields, the security-disclaimer preamble, or that raw_json requires an operator-enabled token.

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 short sentences, front-loaded with the action and followed by the conceptual gloss. No filler or restatement of the name beyond the first verb, and the explanatory sentences are useful for an unfamiliar entity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 14 optional parameters and no output schema, and the description covers none of the filtering dimensions, defaults, or result shape. It is adequate as a conceptual primer but leaves the agent to read the schema for everything operational.

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 parameter (filter vs search, output, sortfield, extra_params, raw_json) is already documented in the schema. The only added meaning is the mention that prototypes 'define the groups, templates, and interfaces', which loosely maps to the select* extra_params, so 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 names a specific verb and resource ('Retrieve host prototypes') and spends two sentences explaining what a host prototype is (LLD-created host templates with groups/templates/interfaces). That makes the entity's role clear, but it never distinguishes this tool from close siblings such as discoveryrule_get, drule_get, or dhost_get.

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 guidance and no named alternative. The LLD context hints that this relates to discovery rules, but an agent is not told when to call hostprototype_get rather than discoveryrule_get or host_get, nor any prerequisite such as knowing the LLD rule ID.

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