Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Proxy Delete

proxy_delete
Destructive

Permanently delete Zabbix proxy definitions by proxy ID. Reassign hosts from removed proxies to another proxy or the server; proxy data is typically retained.

Instructions

Delete proxies from Zabbix.

Permanently removes proxy definitions. Hosts assigned to deleted proxies will need to be reassigned to other proxies or the server. Data from deleted proxies is typically retained.

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": {
      "proxyids": "<proxyids>"
    },
    "name": "proxy_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
proxyidsYesProxy IDs to delete.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • addedInput schema / properties / proxyids / minItems
      Added value: +1
  2. First observedv0.5.3

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description adds real value beyond that: it warns that host assignments break and must be reassigned, and that proxy data is typically retained — consequences an agent cannot infer from annotations alone. It stops short of saying what happens on invalid IDs or partial batch failure.

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?

Three short sentences, front-loaded with the action and its permanence, followed by the two operational consequences. No filler or repetition.

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?

The presence of an output schema removes the need to describe return values, and annotations cover the safety profile, so the description's coverage of permanence and host reassignment fills the main gap. A note on how to obtain proxy IDs or behavior on nonexistent IDs would make it complete.

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% with a single required 'proxyids' array already documented as 'Proxy IDs to delete.' The description adds no format, source, or batching guidance beyond that, so the baseline 3 applies.

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 and resource ('Delete proxies from Zabbix') and reinforces scope with 'Permanently removes proxy definitions.' An agent can immediately distinguish this from proxy_get, proxy_create, and proxy_update in the sibling list.

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 implied by the destructive verb, but the description never states when to use this versus alternatives (e.g., proxy_update to repoint a proxy) or that proxy IDs must first be obtained via proxy_get. No explicit prerequisites or exclusions are given.

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