Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Proxy Update

proxy_update

Modify an existing Zabbix proxy by updating its name, operating mode, or description; specify only the fields you need to change.

Instructions

Update an existing proxy in Zabbix.

Modifies properties of an existing proxy. You can change the name, operating mode, or description. 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": {
      "proxyid": "<proxyid>"
    },
    "name": "proxy_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew proxy name/hostname.
proxyidYesID of the proxy to update.
descriptionNoNew description.
operating_modeNo0=active, 1=passive.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 declare readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description adds real context beyond them: unspecified fields are left unchanged, which tells the agent this is a safe partial mutation. It omits consequences the agent would want, such as what happens to hosts assigned to a proxy when operating_mode flips, or name-uniqueness constraints.

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?

Short and front-loaded, with the action stated in the first sentence. The second sentence partly restates the first ("Modifies properties of an existing proxy"), costing a little redundancy, but overall it is compact.

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 four-parameter mutation with full schema coverage, annotations, and an output schema, the description covers what the tool does and how minimally to call it. Only the side effects of a proxy-mode change are left unexplained, which is a minor gap.

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 the schema already documents all four parameters including the 0=active/1=passive encoding. The description restates the same field list (name, operating mode, description) without adding format, constraints, or edge-case meaning beyond the schema. 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?

Names a specific verb and resource ("Update an existing proxy in Zabbix") and enumerates the mutable fields, so the agent knows exactly what changes. It does not explicitly contrast with proxy_create/proxy_delete/proxy_get siblings, though the verb alone makes the distinction fairly obvious.

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" gives useful partial-update guidance that implies this is an edit-in-place operation. However, there is no statement of prerequisites (proxy must already exist, valid proxyid), no exclusions, and no explicit routing to sibling tools.

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