Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Host Update

host_update
DestructiveIdempotent

Update an existing Zabbix host's technical or visible name, monitoring status, description, linked templates, or proxy; only specified fields are changed.

Instructions

Update an existing host in Zabbix.

Modifies properties of an existing host. You can change the technical name, visible name, status (enable/disable monitoring), description, linked templates, or the proxy that monitors it. Only specify the fields you want to change.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hostid": "<hostid>"
    },
    "name": "host_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoNew technical name.
nameNoNew visible name.
hostidYesID of the host to update.
statusNo0=enabled, 1=disabled.
proxyidNoProxy to monitor the host through. '0' moves monitoring back to the Zabbix server; blank leaves it unchanged.
templatesNoReplaces ALL linked templates (e.g., [{'templateid': '10001'}]). Templates left out are unlinked; their items and triggers stay on the host.
descriptionNoNew description.
templates_clearNoTemplates to unlink AND clear - their items, triggers and collected data are deleted from the host.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.1
    • addedInput schema / properties / proxyid
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Proxy to monitor the host through. '0' moves monitoring back to the Zabbix server; blank leaves it unchanged."
      +}
    • addedInput schema / properties / templates
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "additionalProperties": {
      +          "type": "string"
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Replaces ALL linked templates (e.g., [{'templateid': '10001'}]). Templates left out are unlinked; their items and triggers stay on the host."
      +}
    • addedInput schema / properties / templates_clear
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "additionalProperties": {
      +          "type": "string"
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Templates to unlink AND clear - their items, triggers and collected data are deleted from the host."
      +}
  2. First observedv0.5.3

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=true, and the description adds partial-update semantics beyond that. It does not itself disclose that template changes unlink templates or delete collected data (that lives only in the schema), nor does it mention permission requirements or the effect of omitted fields beyond the generic instruction.

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 with the core action front-loaded and the partial-update rule placed last where it is most actionable. The middle sentence slightly overlaps the first in listing properties, but there is no real padding.

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 and full schema coverage, the description only needs to frame the operation, which it does adequately. The remaining gap is behavioral rather than structural: side effects of template replacement and required auth level are left to the schema and annotations.

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 is already documented, including the destructive semantics of templates and templates_clear. The description restates the set of editable fields but adds no syntax, format, or edge-case detail beyond what the schema provides, 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?

States a specific verb and resource ("Update an existing host in Zabbix") and enumerates the mutable properties, which makes clear it is the mutation counterpart to host_create/host_delete. It never explicitly differentiates itself from those siblings in text, relying on the reader to infer from the name.

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?

"Only specify the fields you want to change" is genuinely useful partial-update guidance. However, there is no explicit statement of when to use this versus host_create, host_delete, or template_update, and no prerequisites (e.g., permissions, host must exist) are mentioned.

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